Problem importing JMS binding
Hello,
when importing WSDL's with JMS binding from the TMF MTOSI standard files I realized that no operations were imported. For the HTTP bindings everything worked normally.
Furthermore I got following error in the soapUI log:
The soap:binding part looks as follows in the files from the standard:
After some googling I found an implementation description of the SoapJMSBindingImporter, in which I could see that the following strings are accepted for the transport URI: "http://www.soapjms.org/2007/08/soap/bindings/JMS/" or "http://www.w3.org/2008/07/soap/bindings/JMS/".
So I changed the soap:binding part in the WSDL of the standard as follows:
After that I could import the WSDL properly and the operations were available in soapUI.
Now to my question:
Shouldn't "http://schemas.xmlsoap.org/soap/jms" be a valid string for JMS tranport too?
Or is the standard possibly just wrong at this point?
Best Regards
when importing WSDL's with JMS binding from the TMF MTOSI standard files I realized that no operations were imported. For the HTTP bindings everything worked normally.
Furthermore I got following error in the soapUI log:
Tue Jan 24 15:00:55 CET 2012:INFO:Missing importer for {http://www.tmforum.org/mtop/fmw/wsdl/notb/v1-0}NotificationBrokerSoapJmsBinding
The soap:binding part looks as follows in the files from the standard:
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/jms"/>
After some googling I found an implementation description of the SoapJMSBindingImporter, in which I could see that the following strings are accepted for the transport URI: "http://www.soapjms.org/2007/08/soap/bindings/JMS/" or "http://www.w3.org/2008/07/soap/bindings/JMS/".
So I changed the soap:binding part in the WSDL of the standard as follows:
<soap:binding style="document" transport="http://www.w3.org/2008/07/soap/bindings/JMS/"/>
After that I could import the WSDL properly and the operations were available in soapUI.
Now to my question:
Shouldn't "http://schemas.xmlsoap.org/soap/jms" be a valid string for JMS tranport too?
Or is the standard possibly just wrong at this point?
Best Regards
