This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 26625 - Can't open server.xml for editing after switching projects
Summary: Can't open server.xml for editing after switching projects
Status: VERIFIED FIXED
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Tomcat (show other bugs)
Version: 3.x
Hardware: PC Windows ME/2000
: P2 blocker (vote)
Assignee: Milan Kuchtiak
URL:
Keywords:
Depends on:
Blocks: 29755 31920
  Show dependency tree
 
Reported: 2002-08-19 22:26 UTC by Isaac Arias
Modified: 2005-12-09 10:21 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Isaac Arias 2002-08-19 22:26:31 UTC 
The "Configure (Edit server.xml)" menu item in the Server 
Registry > Installed Servers > Tomcat 4.0 > Internal pop-
up menu does not work after switching projects.

To reproduce, open the IDE. Switch to a different project 
using the Project > Project Manager menu item from the 
menu bar. After the new project is open, select 
the "Configure (Edit server.xml)" for the Tomcat Internal 
server in the Runtime tab. Nothing happens.
Comment 1 Milan Kuchtiak 2002-08-23 09:43:21 UTC 
Now I can only confirm the issue.
I am going to investigate it further.
Comment 2 Milan Kuchtiak 2002-08-23 10:58:26 UTC 
I investigated the issue. The bug is somewhere in
org.openide.text.CloneableEditor.
There is an open() method which does nothing, because discard() method
returns false - it's because the support.env().isValid() returns false
after switching projects.
Comment 3 Peter Zavadsky 2002-12-04 16:35:57 UTC 
Yes it is not opening because the support env returns it is invalid.
And the support is of type:
org.netbeans.modules.web.xmlutils.XMLJ2eeEditorSupport
and environment of type:
org.netbeans.modules.web.xmlutils.XMLJ2eeEditorSupport$XmlEnv

Investigate why they are invalid, if they shouldn't be.

Reassigning back.

Note: I also added logging in CloneableEditor for such cases to see it
directly on console.
(openide/../text/CloneableEditor.java 1.51)
Comment 4 Milan Kuchtiak 2003-02-21 19:06:33 UTC 
Switching to another project has an effect that 
Tomcat40DataObject is invalidated, together with 
org.netbeans.modules.web.xmlutils.XMLJ2eeEditorSupport$XmlEn
v
We need to investigate this issue farther.
Comment 5 Milan Kuchtiak 2003-02-28 10:47:21 UTC 
tomcat40_base/conf filesystem shouldn't be unmounted when 
projects are being switched. This caused the invalidation 
of the Tomcat40DataObject .

Special TomctFileSystem was created which is resistant 
against the project switching.

Fixet to trunk. 02/28/2003.
Need to be checked into release35 branch.
Comment 6 Milan Kuchtiak 2003-02-28 14:03:16 UTC 
Increased the priority to P2, because after switching 
projects, the tomcat functionality is rather limited.

Not only server.xml file can't be opened - also the web 
module can't be executed in new project - see #29755.
Comment 7 Milan Kuchtiak 2003-02-28 17:03:07 UTC 
Fixed also in release35 branch.
Comment 8 Milan Kuchtiak 2003-02-28 17:08:54 UTC 
I forgot to change the status.
Comment 9 Jaroslav Pospisil 2005-12-09 10:21:17 UTC 
VERIFIED