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.
The following test scenario illustrates the issue: * create new j2ee module * open sun xml editor * shutdown ide * open ide * open another sun xml editor - now should be two * open again (another will not be opened). The main issue with this is that we need xmleditor support to be linked with the ConfigDataObject to support refreshing the xml editor using the ConfigurationStorage.save method.
Martin, Chris and I have a near complete fix for this that we delay to put into promoe_ea1 on the day of hard code freeze. Would you mind if I take ownership of this?
Sure, go ahead. Thanks.
Of course, thanks!
Now I realized you were writing about XML editor. I fixed problem on this place already in trunk some time ago. Now when you open IDE again after shutdown with open XML editor and try Edit, opened XML editor will be focused. Please see issues 49033 and 40534.
Nam, is this the issue we are working on. This is not the memory leak issue, but the failure to link the xml configuration editor being used with the ConfigDataObject if the editor is left open after restart. The issue here is that the synchronization of xml editor will fail if there are xml config editors which are not associated with the ConfigDataObject. The save refresh is currently being done through the save cookie. To verify this problem is really fixed the following test should be run. 1. create ejb module project 2. open xml config editor on the sun-ejb-jar.xml 3. add ejb -- notice that the config editor is refreshed. 4. shutdown ide. 5. restart ide. 6. add another ejb. The visible config editor should be refreshed.
Obviously this is not the memory leak issue that I am interested in working on. Sorry, I mixed up. I will identify the other one and enlist on it and leave this one for Martin.
Chris, I tested this on last J2EE build and looks it's working. Is it OK for you to close it as fixed?
*** This issue has been marked as a duplicate of 40534 ***
Looks fixed to me!