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.
NB 6.0 Beta 2 doesn't support .NET generated WSDLs with SOAP 1.1 bindings. The autogenerated by .NET WSDL contains both SOAP 1.1 and SOAP 1.2 binding but cannot be used as is. The IDE throws runtime error when deploying under default glassfish bundled container: Exception: Unsupported Content-Type: application/soap+xml; charset=utf-8 Supported ones are: [text/xml] See a similar error discussed in this thread: http://www.nabble.com/Web-service-error---NB6.0-B2-t4718769.html Related Subcomponents: jaxws, wsit
Kindly attach the wsdl to this bug (URL will also do). I have seen a similar problem where the wsdl specifies a SOAP 1.1 message (look at the namespace of the SOAP binding in the wsdl) and yet the service returns a message that is SOAP 1.2 formatted.
Netbeans/JAXWS does support both SOAP 1.1 and SOAP 1.2. In the problem we encountered with Axis (resulting in a similar error message), the response message from the Axis web service was formatted in SOAP 1.2 yet the WsDL specified 1.1. Thus, the client (JAXWS) was "accepting" (via the ACCEPT html header) SOAP 1.1 message (text/xml content type) but it received a SOAP 1.2 message (content-type is application/soap+xml), thus the error message.
Created attachment 52768 [details] BusinessPartnersService wsdl
Created attachment 52769 [details] LoginService wsdl
Is there a way to test the client, i.e. make a call to the service? The service address currently specifies localhost. It would be helpful if we can call the actual service since this is a runtime error. We will need to find out the format of the response message from the .NET service.
I noticed IDE doesn't generate @BindingType annotation in implementation class (in WS from WSDL case) for SOAP1.2 binding IDE should generate something like : @WebService(serviceName = "BusinessPartnersService", portName = "BusinessPartnersServiceSoap12", ...) @BindingType(value=SOAPBinding.SOAP12HTTP_BINDING) Isn't this the problem ?
This problem is with regards to the client only. The web service (as I understand it from Marina--Marina please correct me if I am wrong) is implemented in .NET and is published somewhere (still getting this info from Marina). Thus we do not have control over the web service itself. This is an interoperability issue between a JAXWS client and a .NET web service. Thanks.
Yes, from the client perspective SOAP11 and SOAP1.2 make no difference.
I tested the JAXWS client using the two stubs (one for the SOAP1.1 binding and the other for the SOAP 1.2 binding). In the case of the SOAP 1.1 binding it was correctly accepting and expecting a "text/xml" content-type. In the case of the SOAP 1.2 binding it was correctly accepting and expecting a "application/soap+xml" content-type. This proves that the JAXWS client is able to send and receive the correct SOAP message in both cases. I think the problem is that the .NET service is not sending the correct SOAP message type. That is, when a client call that uses the SOAP 1.1 binding is used the .NET web service sends a SOAP 1.2 formatted message. Closing this bug as INVALID.