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.
Summary: | NPE at VisualizerNode in sun-web.xml DD editor | ||
---|---|---|---|
Product: | webservices | Reporter: | Petr Blaha <blaha> |
Component: | Code | Assignee: | Nam Nguyen <nnguyen> |
Status: | VERIFIED FIXED | ||
Severity: | blocker | ||
Priority: | P2 | ||
Version: | 4.x | ||
Hardware: | Sun | ||
OS: | SunOS | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: | Stack trace |
Description
Petr Blaha
2004-09-14 13:02:26 UTC
Created attachment 17614 [details]
Stack trace
Unable to reproduce After an hour work with NB I got this issue, but I can't provide steps to reproduce. I'm lowering priority. Issue was reproduced in Build 040918. seeing the same exception in case of sun-ejb-jar.xml steps to reproduce: 1) create new ejb module 2) add session ejb to it 3) open editor for sun-ejb-jar.xml(double click on sun-ejb-jar.xml) 4) put some values(eg bean pool properties) 5) save and close sun-ejb-jar editor 6) build ejb module project 7) open editor for sun-ejb-jar.xml(double click on sun-ejb-jar.xml) 8) try to expand <Sun EJB Jar> node in the left-hand side of the editor High visible error, therefore I'm increasing prioroty. Looks like an issue related to OS type. I am able to reproduce on Windows 2000(for sun-ejb-jar.xml); not able to reproduce for on Window XP did you look at the root cause of the issue: What is under org.openide.explorer.view.VisualizerNode.<init>(VisualizerNode.java:130) to create a NPE... Might not be a platform issue, but a timing/threading issue? Remove all issues from temporary component. *** Issue 52249 has been marked as a duplicate of this issue. *** QE team requested fix the issue in EA1 release. However, the fix isn't still avalaible. I'm changing status whiteboard to EA2. In EA1 Nam reviewed & checked in the workaround. It is regression. It seems it has not made into EA2 trunk. Assigning this to Nam. I spoke to Nam, he will try to fix it or if not possible he will merge the workaround from EA1 branch to EA2/Qbuild. Work-around code is now in EA2 branch. Return new node for each call to ConfigBeanStorage.getNode() is not very efficient, anyway it works for EA2. Merged to trunk: Checking in src/org/netbeans/modules/j2ee/deployment/config/ConfigBeanStorage.java; /cvs/j2eeserver/src/org/netbeans/modules/j2ee/deployment/config/ConfigBeanStorage.java,v <-- ConfigBeanStorage.java new revision: 1.15; previous revision: 1.14 done Processing log script arguments... More commits to come... Checking in src/org/netbeans/modules/j2ee/deployment/config/ui/ConfigBeanNode.java; /cvs/j2eeserver/src/org/netbeans/modules/j2ee/deployment/config/ui/ConfigBeanNode.java,v <-- ConfigBeanNode.java new revision: 1.13; previous revision: 1.12 I was working with QE2 build 20050112 last day and wasn't able to reproduce the bug. Therefore, I mark issue as verified. |