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.
Build: NetBeans IDE Dev (Build 200810090201) VM: Java HotSpot(TM) Client VM, 10.0-b23, Java(TM) SE Runtime Environment, 1.6.0_07-b06 OS: Windows XP, 5.1, x86 User Comments: wobster: trying to edit wsdl file wobster: trying to edit wsdl file Stacktrace: java.lang.NullPointerException at org.netbeans.modules.websvc.wsitconf.ui.client.ClientView.<init>(ClientView.java:159) at org.netbeans.modules.websvc.wsitconf.ui.client.ClientTopComponent.doInitialize(ClientTopComponent.java:131) at org.netbeans.modules.websvc.wsitconf.ui.client.ClientTopComponent.addNotify(ClientTopComponent.java:154) at java.awt.Container.addNotify(Container.java:2592) at javax.swing.JComponent.addNotify(JComponent.java:4683) at java.awt.Container.addNotify(Container.java:2592)
Created attachment 71498 [details] stacktrace
Build: NetBeans IDE Dev (Build 200810091401) VM: Java HotSpot(TM) Client VM, 10.0-b23, Java(TM) SE Runtime Environment, 1.6.0_07-b06 OS: Windows XP, 5.1, x86 User Comments: just checking latest version. Trying to edit web service references after generating a web service client. Stacktrace: java.lang.NullPointerException at org.netbeans.modules.websvc.wsitconf.ui.client.ClientView.<init>(ClientView.java:159) at org.netbeans.modules.websvc.wsitconf.ui.client.ClientTopComponent.doInitialize(ClientTopComponent.java:131) at org.netbeans.modules.websvc.wsitconf.ui.client.ClientTopComponent.addNotify(ClientTopComponent.java:154) at java.awt.Container.addNotify(Container.java:2592) at javax.swing.JComponent.addNotify(JComponent.java:4683) at java.awt.Container.addNotify(Container.java:2592)
Created attachment 71519 [details] stacktrace
Would you please attach the WSDL file or better the whole project? I can't do much without it.
Not able to reproduce.
I still saw the null pointer exception in the Beta release as well. I can't release the XMLSchema to you since it is proprietary, but if there is some logging I can turn on to help you trace down the NPE, let me know.
Getting there through logging might not be a simple process due to the complexity of the files, so I think without any files from you it's hard to get to the real cause. Would it be possible for you to provide a simpler files (remove anything proprietary or not from the files such that the exception is still present)? Btw, the code on the line which could cause exception is '... binding.getName() ...' which does indicate that the issue might be connected to the binding names in your wsdl. Would you please check that? Thanks.
Closing as worksforme due to no response from reporter.