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
Roa,
I'm confused, are you implying that there is not a bug in SoapUI when importing a WSDL that is using SOAP 1.2 and JMS bindings? It clearly doesn't import any operations.
These same operations show up if importing a WSDL using SOAP 1.1 and JMS binding, it also correctly imports if using SOAP 1.2 and HTTP bindings. Why don't they import when using SOAP 1.2 and JMS?
The only insight on what has gone wrong is seeing,
Yes there is a workaround, but it took me hours to figure out the cause. Ideally SoapUI would just work since the WSDL is compliant.
Is this not the proper place to report bugs?
I'm confused, are you implying that there is not a bug in SoapUI when importing a WSDL that is using SOAP 1.2 and JMS bindings? It clearly doesn't import any operations.
These same operations show up if importing a WSDL using SOAP 1.1 and JMS binding, it also correctly imports if using SOAP 1.2 and HTTP bindings. Why don't they import when using SOAP 1.2 and JMS?
The only insight on what has gone wrong is seeing,
INFO [WsdlImporter] Missing importer for...in the log. Not real informative on the cause. If the log mentioned,
SOAP 1.2 is not importable with JMS binding, change to HTTP bindingat least I would have a clue on the cause and an approach to "fixing" the issue.
Yes there is a workaround, but it took me hours to figure out the cause. Ideally SoapUI would just work since the WSDL is compliant.
Is this not the proper place to report bugs?