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.
When I pointed to GoogleSearch.wsdl file (on my deskotp) in the Web Service from WSDL wizard, it threw a null pointer exception. I couldn't proceed.
Please, attach the wsdl file
you can use any rpc/enc ws (eg famous bgtrans from xmethods.com) - it's caused by the fact that JAX-WS does not support rpc/enc webservices... (thrown exception contains something like "JAX-WS does not support rpc/enc...") - maybe it would be enough to change the exception dialog with some error message
Related also to issue 73856. We should likely prevent to create client node for that service .. and inform user in error message what's the problem.
Created attachment 30135 [details] WSDL causing null pointer exception.
For Web Service Client : The client node is marked by error badge. (issue 73856) For Web Service from WSDL we shouldn't allow to "Finish" wizard. The Warning message appears instead of exception. Diffs: http://websvc.netbeans.org/source/browse/websvc/dev/src/org/netbeans/modules/websvc/dev/wizard/WebServiceFromWSDLPanel.java?r1=1.1.2.11&r2=1.1.2.12 http://websvc.netbeans.org/source/browse/websvc/dev/src/org/netbeans/modules/websvc/dev/wizard/Bundle.properties?r1=1.17.4.3.2.11&r2=1.17.4.3.2.12
Created attachment 30143 [details] warning message - sample
Ccing Ken to help with the error message wording. The current message is attached in "service- warning.jpg". Thanks. The dialog should be "error" not warning because the user cannot finish the wizard. Also, there should be an inline error message informing the user why she cannot click the finish button. A shorter version of the error message. Ken, can you help with that? Thanks. Don't forget the user could write the wsdl path manually into the text field. Reopening as P3.
OK, reassigning to R.Najman
Ken, could you provide the error messages and then reassign back to me, please? Thanks.
reassigning to geertjan, who looks after WSDL doc issues
What should the user do to fix the problem? That's important to know and it is information that should be included in the error message.
Obsolete milestone, please reevaluate
Rico, pls provide the text to Geertjan
we now allow creation of JAX-RPC clients in Java EE 5 projects to support this use-case. Closing as fixed.