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.
Cannot create WS from attached WSDL. Not sure where is the problem, the WSDL seems right.
Created attachment 42145 [details] WSDL
I tried 5.5.1 and 6.0, on JDK1.5. The wizard tells me there's no service in the WSDL.
That's because JAX-WS itself cannot find any usable service nor port in this wsdl: lukas@pomeray:~/testing$ /space/java/jaxws-ri/bin/wsimport.sh -version -Xendorsed JAX-WS RI 2.1.1-04/12/2007 02:26 PM(vivekp)-RC1 lukas@pomeray:~/testing$ /space/java/jaxws-ri/bin/wsimport.sh -d xxx -verbose -Xendorsed PolicyService.wsdl parsing WSDL... [ERROR] Invalid wsdl:operation "Normalize": its a document-literal operation, message part must refer to a schema element declaration line 24 of file:/home/lukas/testing/PolicyService.wsdl lukas@pomeray:~/testing$ /space/java/jaxws-ri/bin/wsimport.sh -d xxx -verbose -Xendorsed -extension PolicyService.wsdl parsing WSDL... [WARNING] ignoring operation "Normalize": message part does not refer to a schema element declaration line 24 of file:/home/lukas/testing/PolicyService.wsdl [WARNING] ignoring operation "Intersect": message part does not refer to a schema element declaration line 28 of file:/home/lukas/testing/PolicyService.wsdl [WARNING] ignoring operation "Merge": message part does not refer to a schema element declaration line 32 of file:/home/lukas/testing/PolicyService.wsdl [WARNING] Port "PolicyPort" does not contain any usable operations line 71 of file:/home/lukas/testing/PolicyService.wsdl [WARNING] Service "PolicyService" does not contain any usable ports. try running wsimport with -extension switch. line 70 of file:/home/lukas/testing/PolicyService.wsdl generating code... com/example/ws/_2004/_09/policy/Any.java com/example/ws/_2004/_09/policy/ObjectFactory.java com/example/ws/_2004/_09/policy/package-info.java lukas@pomeray:~/testing$
Filed new issue against JAX-WS RI: https://jax-ws.dev.java.net/issues/show_bug.cgi?id=319
Depends also on : https://jax-ws.dev.java.net/issues/show_bug.cgi?id=100
The WSDL is not compliant with Basic Profile guidelines. The JAXWS runtime takes a hard line against such WSDLs, that is, it rejects it. The non-compliance is due to the use of the "type" attribute in the message/part definition of the "Any" message. The binding then specifies a doc/literal style. The guideline says that if the binding style is doc/literal, the attribute "element" (and thus pointing to a schema element) should be used in the message/part definition. As explained by Vivek (the JAXWS engineer) in https://jax-ws.dev.java.net/issues/show_bug.cgi?id=319, they have no plans of supporting this because there is no spec that specifies how to marshal/unmarshal such WSDL. Closing as INVALID.