Import Error with JMS Binding and SOAP 1.2
When I import a WSDL that is using a JMS Binding http://www.w3.org/2008/07/soap/bindings/JMS/ using SOAP 1.1, all the operations are imported as expected. when I change the same WSDL over to ...
Forum Discussion
What I believe is that the purpose of providing a concrete wsdl file to the clients / users to start their work independent of server side work. And once client have the wsdl, they can use different tools to generate the stubs and client code of their choice.
Some tools may need specific wsdl either meant for http or jms. However, in soapui, one can use http wsdl and jms endpoint.
All both differs would be the transport mechanism, and inline schema remains the same.
Some tools may need specific wsdl either meant for http or jms. However, in soapui, one can use http wsdl and jms endpoint.
All both differs would be the transport mechanism, and inline schema remains the same.