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 # : 200710180000 ] [ JDK VERSION : 1.6.0_01 ] I have a WSDL I downloaded from: http://www.exchangenetwork.net/node/node_products.htm link: http://www.exchangenetwork.net/node/Node20Draft8Documents.zip It is in the archive. Anyways, the web service from WSDL wizard tells me there is not a port defined and will not let me consume this WSDL. The WSDL should be fine though as it has been consumed by the working group at www.exchangenetwork.net which has Java and .NET clients for it. I will attach the WSDL to this issue to make it easier, but have included the links for more information about what the web services purposes are and what it is I'm trying to do.
Created attachment 51704 [details] This is the WSDL with the issue
I was able to generate JAX-WS service for the attached WSDL. However, I got a bunch of warnings like these : [WARNING] SOAP port "NetworkNodePort2": uses a non-standard SOAP 1.2 binding. line 606 of file:/usr/local/home/mkuchtiak/NetBeansProjects/JavaApplication1/xml-resources/web-service-references/NetworkNode2/wsdl/localhost_8080/WebApplication1/NetworkNode2.wsdl [WARNING] R2716 WSI-BasicProfile ver. 1.0, namespace attribute not allowed in doc/lit for soapbind:body: "Authenticate" line 485 of file:/usr/local/home/mkuchtiak/NetBeansProjects/JavaApplication1/xml-resources/web-service-references/NetworkNode2/wsdl/localhost_8080/WebApplication1/NetworkNode2.wsdl [WARNING] R2716 WSI-BasicProfile ver. 1.0, namespace attribute not allowed in doc/lit for soapbind:body: "Authenticate" line 488 of file:/usr/local/home/mkuchtiak/NetBeansProjects/JavaApplication1/xml-resources/web-service-references/NetworkNode2/wsdl/localhost_8080/WebApplication1/NetworkNode2.wsdl ... Seems, the wsdl file doesn't conforms the WS-I Bacic Profile. Especially, see the namespaces warnings. Nevertheless, I tried to implement the web service and deploy to GlassFish application server. Deployement worked fine. When I tried to call getServices() operation in java client I got : com.sun.xml.ws.client.ClientTransportException: The server sent HTTP status code 415: Unsupported Media Type at com.sun.xml.ws.transport.http.client.HttpClientTransport.checkResponseCode(HttpClientTransport.java:252) at com.sun.xml.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:151) at com.sun.xml.ws.transport.http.client.HttpTransportPipe.processRequest(HttpTransportPipe.java:88) at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:595) at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:554) at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:539) at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:436) at com.sun.xml.ws.client.Stub.process(Stub.java:248) at com.sun.xml.ws.client.sei.SEIStub.doProcess(SEIStub.java:134) at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:244) at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:224) at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:117) at $Proxy41.getServices(Unknown Source) I don't think this is a Netbeans problem. Please, ask JAX-WS team for help. What we do in Netbeans, we call JAX-WS:wsimport utility and generate implementation class for the SEI class (Service Endpoint Interface), generated by wsimport. Eventually, report a bug to jax-ws team (https://jax-ws.dev.java.net), and attach the link to this issue. Thanks.
I was playing with this yesterday and during first couple of minutes I was facing this issue. After few hours when I got back to this again it worked fine for me. In both cases I used new user dir and I tried beta2 as well as trunk builds. There seems to be some random timing/refresh issue...
Can you please attach a screen shot or any error message. I never got to any problem. I am using. Java(TM) SE Runtime Environment (build 1.6.0_03-b05) I'll try 1.6.0_01.
Hardly to reproduce. May be some log messages can be added to find the problem.
Works fine for me. I fixed the issue with incorrect detection of SOAP12 binding : http://hg.netbeans.org/main?cmd=changeset;node=22e606a2069d