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. Rightclick "Web Services" node and select "Add Web Service...". 2. Type http://www.webservicex.net/usweather.asmx?WSDL in "WSDL URL" field and click "Add" button. Result: Exception arises and Web Service is not added: "java.lang.NoSuchMethodError: com.sun.tools.ws.processor.modeler.wsdl.WSDLModeler.<init>(Lcom/sun/tools/ws/wscompile/WsimportOptions;Lcom/sun/tools/ws/wscompile/ErrorReceiver;)V at org.netbeans.modules.websvc.api.jaxws.wsdlmodel.WsdlModeler.generateWsdlModel(WsdlModeler.java:178) at org.netbeans.modules.websvc.api.jaxws.wsdlmodel.WsdlModeler.access$000(WsdlModeler.java:50) at org.netbeans.modules.websvc.api.jaxws.wsdlmodel.WsdlModeler$1.run(WsdlModeler.java:75) at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:539) [catch] at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:964)".
We use the NB JAX-WS modeler directly. This exception appears to originate from there.
This looks like a conflict in jaxws class versions. ErrorReceiver is a class that is new in jaxws2.1. It turns out some jaxw20 classes are also in the VWP classpath thru some EE jars. Quy will try to replace the EE jars with the one that has the newer jaxws on Solaris and see if it solves the problem.
Waiting for result of Quy's test on Solaris. Meanwhile marking this as incomplete.
I tested on Solaris 10 SPARC with JDK 1.5.0_06 and JDK 1.6.0. I could not reproduce the issue on either JDK version.
Also tested on JDK 1.6.0_01 with the same result.
Is this using the new EE jars that contain the new jaxws classes or did you mean that you were not able to reproduce this at all?
I was not able to reproduce at all. However, the issue submitter informed me that this issue only occurs on Solaris x86.
Thanks for the update Quy. Kindly ask the reporter to try the workaround, i.e., use updated EE jars that contain new jaxws classes and see if it solves the problem.
This issue is showstopper for M10. Please integrate the fix into the trunk and "release60-m10" branch.
This appears to be a vwp setup problem. Quy is looking into it. Reassigning this to VWP/Quy Nguyen.
I could not reproduce this on Solaris 10 x86 running on JDK 1.6.0_01. Marking as incomplete until there is a reproducible test case.
Does this issue still prevent M10 from being released? "rcruz" set the Target Milestone to "beta1". Can the dependency on M10 umbrella issue be removed?
I installed 1.6.0_01 and build 200706251444 and everything is fine now. Probably the problem was in jdk, before I tested with 1.6.0-beta2.
Verified with build 200706251444.