Forum Discussion

gherr's avatar
gherr
Occasional Contributor
15 years ago

Wrong SOAP Action set on JMS Transport.

Hi and a happy new year!

There is a bug in JMS transport, as it does not recognize the SOAP Action value from the WSDL. If the option "add soap action as property" is checked, the operation name is added as SoapAction property to the message header instead of the correct value from WSDL as defined in the specs.

JMS property names are case sensitive and some platforms, such as TIBCO BusinessWorks, expect the property in a different case (SOAPAction instead of SoapAction). Adding this variant to the message would increase interoperability with such "non-standard" systems.

I have fixed the soapAction property handling in 3.6.1 and included the patch below.

I would appreciate, if you could include this into the next release.

Thanks.

Gabor
  • credean's avatar
    credean
    15 years ago
    Hi all,

    The point from Gabor is valid and the SOAP Action must be set to the correct value from the WSDL as defined in the specification.
    Additionally setting the SOAPAction in the JMS Header Property will make soapUI compatible with the iProcess Service Agents and the Web Service Agents from TIBCO Business Works.

    This will add a great value to the soapUI tool and will differentiate it from the other tools.

    Thank you.
    Calin
  • hemangajmera's avatar
    hemangajmera
    New Contributor
    14 years ago
    Is there anyway to have this included? Any place to vote?
    Thanks to gherr for providing the patch. After this, it should be easy.