I'm using some examples from netbeans tutorials to develop some soap services.
https://netbeans.org/kb/docs/websvc/jax-ws.html
Now my question is
1) where do we configure that our app/service is soap 1.1 compatible or soap 1.2 compatible.
I'm using netbeans 7.3.1 with jdk 7.25 and glassfish 4.0.
Solution: you can bind your implementation class to SOAP 1.2 using :
#BindingType(javax.xml.ws.soap.SOAPBinding.SOAP12HTTP_BINDING)
You can confirm soap 1.2 binding by looking at your wsdl which will have tags like
Related
I create a client in Domino to consume a web service that works with SOAP 1.2 and has HTTPBinding.
The client generation tool for Domino Designer Web services an error is displayed when trying to generate reporting that the SOAP accepted version is 1.1.
I decided to create the client with CXF framework through tool wsdl2java. In an agent I used these classes to consume the web service, however the below error was displayed. I think it's because of the SOAP version, but I'm not sure.
com.sun.xml.internal.ws.protocol.soap.MUTube getMisUnderstoodHeaders
INFO: Element not understood={http://www.w3.org/2005/08/addressing}Action
Also generated a jar of classes generated by wsdltojava and imported to another agent, but the error below is displayed.
java.lang.UnsupportedClassVersionError: JVMCFRE003 bad major version; class=, offset=6
The question is, no way consume a web service with SOAP 1.2 in Domino only supports up to version 1.1?
Thanks a lot!
I don't believe that Domino's web service consumer supports SOAP 1.2 at this time. You might be able to do what you need with an agent though - here's one way: How can I call a SOAP 1.2 Web service from a LotusScript agent?
In fact there is no way to natively consume a web service with soap version 1.2. There are already several requests from IBM to upgrade the SOAP version. What I did, was to develop a new layer through a new web service with the version SOAP 1.1, which internally calls the web service with the SOAP version 1.2;
Does anybody have an idea about this issue or could somebody point me to a example SOAP server app code built in Zend 2.0.
I wanted some clarification regarding SudzC for iPhone. Does SudzC support SOAP 1.2?
I tried using SudzC with the web service http://www.restfulwebservices.net/wcf/CurrencyService.svc?wsdl and it works fine but with my web service it doesn't. The only difference I can spot is that the above service uses SOAP1.1 while mine used 1.2.
Regards,
EC
You pretty much answered your own question. A service expecting a soap 1.2 message is not required to be backward compatible to soap 1.1 formatted messages. You can configure WCF to accept soap 1.1 messages by creating a custom binding as show here. Although that WCF config is for a client, you can also configure a service to use that custom binding. If the service needs to support soap 1.2 messages, you can just leave your existing endpoint configured as-is and create a new endpoint for the soap 1.1 custom binding.
Is there are any wsdl-validation profiles available to check the ws-i compliance of wsdl file with soap 1.2?
Or I need to switch to soap 1.1 to pass the WS-I compliance test?
I believe you can use the following tools to test your service. I guess they should also work for SOAP 1.2 (haven't tried it though).
You could try to use the tools by themselves but I think it would be easier to do it with SoapUI. If I'm not mistaken, the BSP Test Tools is what's used by default by SoapUI to test WS-Interoperability.
Good luck!
We're using Oracle 10g application server and deployed the Web service and trying to deploy the web service client. Server is working fine i.e.; marshalling is working fine. We're getting the output from the service properly but the search client is not unmarshalling (parsing) the response received. We're using all the tags under same name space so there is no name space problem. Different collections would exists in the XSD. Has anyone faced similar kind of issue? Is there any solution for this?
Thanks
Santhosh
Well... the issue was due to the library which was not running as expected in Java 1.5. We've developed the web service client with JAX-WS 2.2 which was running properly when running with Netbeans IDE 6.8 but not on the standalone server. We've downgraded the Netbeans and modified the libraries to JAX-WS 2.1. It worked...
Good to know. JAX-WS 2.2 is not compatible with Java 1.5