Forum Discussion

FranckLucas's avatar
FranckLucas
New Contributor
14 years ago

SOAP/JMS binding transport W3C 4 June 2009

Hi,
SOAPUI currently supports SOAP/JMS and this is really a nice feature, however norms concerning SOAP/JMS are not
yet definitively frozen.
Currently the class com.eviware.soapui.impl.wsdl.support.soap.SoapJMSBindingImporter is able to import SOAP/JMS binding defined
with transportURI "http://www.soapjms.org/2007/08/soap/bindings/JMS/"

Having a look at W3C site, we find the following specification for SOAP/JMS : http://www.w3.org/TR/2008/WD-soapjms-20081121
and http://www.w3.org/TR/2009/CR-soapjms-20090604 (latest one).

The latest specification stands that transportURI should be "http://www.w3.org/2008/07/soap/bindings/JMS/".
The patch is very simple and is somehting like:
 public boolean canImport( Binding binding )
{
List<?> list = binding.getExtensibilityElements();
SOAPBinding soapBinding = WsdlUtils.getExtensiblityElement( list, SOAPBinding.class );
return soapBinding == null ? false : soapBinding.getTransportURI().startsWith(
"http://www.soapjms.org/2007/08/soap/bindings/JMS/" ) || soapBinding.getTransportURI().startsWith(
"http://www.w3.org/2008/07/soap/bindings/JMS/");
}


Do you think it is possible to take into account this patch for next version (3.6) ?
Thanks,
Franck

1 Reply

  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    SmartBear Alumni (Retired)
    Hi Franck,

    Great thanks for making soapUI even better! This will be in the upcoming nightly build of the 3.6 beta..

    regards,

    /Ole
    eviware.com