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.
1. Install WSIT 2. Create a Web service in a web project that points to appserver which has wsit build installed 3. Make sure Navigator is opened, make sure Memory view is on 4. Select WS node, click Edit WS attributes 5. Change something in the UI 6. Open WEB-INF\wsit.xml file in the editor 7. Select WS node, click Edit WS attributes again 8. Continue with changes in the config ui After subsequent changes in the UI, the processor speed is on 100% and memory usage grows rapidly. After some time, OutOfMemory error is thrown. If you do the steps above without navigator opened (or just docked to the tab), everything's fine and the memory usage is not increased. I'll attach the stack trace from navigator.
Created attachment 30336 [details] stack trace
Just to bring some more information about the wsit module. It works on a XDM based WSDL model on top of wsit.xml file, and it updates the file based on some ui configuration, thus every UI config change updatest the xml file.
*** Issue 76192 has been marked as a duplicate of this issue. ***
Pardon my ignorance, but what does it mean "appserver with wsit build installed"? (I am using latest stable glassfish build, do I need something special?) And are the WSIT modules those two with wsit prefix under nb_all/websvc? Thanks.
I am duplicating this issue to Issue #75588 since both of them are mostly about the same (previously described) problem. I am going to reimplement part of the DocumentModel code and the XMLDocumentModel navigator implementation to 5.5 so both issue should be fixed. *** This issue has been marked as a duplicate of 75588 ***
VERIFIED that this problem has been resolved using build 200703291800.