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. create a web application 2. start from java, add web service from scratch 3. add overloaded methods in webservice implementation class 4. right click the webservice node and generate wsdl file The schema defination is wrong. However, when deploy the webservice to glassfish v2, the wsdl retrieved from it is correct. The webservice implementation class and the created wsdl/xsd are attached.
Created attachment 77013 [details] 3 files in it for java , wsdl, xsd
I don't see any problem with that. The wsdl file has some provisional elements, like <xsd:import schemaLocation.../> or <soap:address location... /> but these values are replaced by the server during deployment. What specifically is wrong with the schema definition ?
the wsdl file is correct but the schema file is wrong. In Java file below, the type of parameter of the 2nd 'print' is int. this info is missing in xsd. Also when run jdk 6 tool wsgen, the created schema file is correct and it's different from what netbeans created. @WebService() public class NewWebService { @WebMethod(operationName = "print") @Oneway public void print(@WebParam(name = "parameter") String parameter) { } @WebMethod(operationName = "print_1") @Oneway @RequestWrapper(className = "test.print_1") public void print(@WebParam(name = "parameter") int parameter) { } }
I see the attached schema file is strange. However, I cannot reproduce this issue. I guess, this must be a problem of particular version of JAX-WS (wsgen) used in your project. Tested with GlassFish V2 (JAX-WS version used here is 2.1.3.1) I think, this is not a Netbeans bug but JAX-WS problem. We bundle Netbeans with JAX-WS 2.1.4 version where wsgen works correctly for this example. In case of Web Application with GlassFish V2 target server, the libraries(jar files) from server are used(webservices-tools.jar). In case of Web Application with Tomcat, the JAX-WS library bundled with IDE is used (jaxws-tools.jar) Please, can you send the version of JAX-WS used in your application ? Go to : Project View -> Libraries -> GlassFish V2 -> webservices-tools.jar -> com.sun.tools.ws package -> version.properties (you can copy the content of version.properties)
the content of version.properties is below, build-id=hudson-749 build-version=JAX-WS RI 2.1.3.1-hudson-749-SNAPSHOT major-version=2.1.3.1
The JAX-WS used in GlassFish is fine. Finally I found the problem. It's in the version of JAX-WS api used in JDK1.6. I wasn't able to reproduce since I used jdk1.5. Nevertheless, I am going to fix this issue by setting java.endorsed.dirs JVM property to wsgen ant task. This should be generated automatically. The workaround is this: - change the "wsgen-NewWebService" target in nbproject/jaxws-build.xml in a following way: <target name="wsgen-NewWebService" depends="wsgen-init"> <wsgen fork="true" sourcedestdir="${build.generated.sources.dir}/jax-ws" resourcedestdir="${build.generated.sources.dir}/jax-ws/resources/" destdir="${build.generated.sources.dir}/jax-ws" xendorsed="true" keep="true" genwsdl="true" sei="test.NewWebService"> <classpath path="${java.home}/../lib/tools.jar:${build.classes.dir}:${j2ee.platform.wsgen.classpath}:${javac.classpath}"/> <jvmarg value="-Djava.endorsded.dirs=${jaxws.endorsed.dir}"/> </wsgen> </target> Note: the "fork" attribute must also be added to force wsgen using another JVM than IDE is running on. Sorry for inconveniency.
The bug is still valid and proposed solution doesn't work. jaxws.endorsed.dir property is not defined.
seems valid for 3.1.2.2 and jdk7. with suggested sample I got 'int' parameter in xsd only after deployment. also tried workaround above without success.
This old bug may not be relevant anymore. If you can still reproduce it in 8.2 development builds please reopen this issue. Thanks for your cooperation, NetBeans IDE 8.2 Release Boss