axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sagara Gunathunga (JIRA)" <>
Subject [jira] [Commented] (AXIS2-5480) SOAPAction being set even when WSDL has soapAction=""
Date Sun, 03 Feb 2013 15:18:14 GMT


Sagara Gunathunga  commented on AXIS2-5480:

Last comment is due to a mistake I did, I used wrong issue id when applying patch to a different
issue. Please ignore last comment generated by Jenkins.
> SOAPAction being set even when WSDL has soapAction=""
> -----------------------------------------------------
>                 Key: AXIS2-5480
>                 URL:
>             Project: Axis2
>          Issue Type: Bug
>          Components: wsdl
>    Affects Versions: 1.6.2
>            Reporter: Wayne Holmes
>         Attachments: IMSWebService.wsdl
> Upgraded our Web Service to use CXF 1.5.5 and our existing AXIS2 clients fail out with
> - The given SOAPAction
does not match an operation.
> Based on the comments in the security fix in CXF 1.5.5, it appears CXF is expecting the
SOAPAction to be "" since that is what is in the CXF generated WSDL. (See
> We did a trace with CXF, SoapUI and .Net clients, and those clients all specify a SOAPAction=""
in the headers.
> Deepal Jayasinghe ended up suggesting that I write this bug and attach a copy of our
WSDL. Complete history of various workaround attempted may be found in the AXIS mailing list
with subject "SOAPAction value in AXIS generated stubs causing problems with server upgrade
to CXF 1.5.5 from CXF 1.5.0". 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message