[
https://issues.apache.org/jira/browse/AXIS-2887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13566620#comment-13566620
]
Wayne Holmes commented on AXIS-2887:
------------------------------------
Version of AXIS 2 used is 1.6.2
> SOAPAction being set even when WSDL has soapAction=""
> -----------------------------------------------------
>
> Key: AXIS-2887
> URL: https://issues.apache.org/jira/browse/AXIS-2887
> Project: Axis
> Issue Type: Bug
> Components: WSDL processing
> Reporter: Wayne Holmes
> Attachments: IMSWebService.wsdl
>
>
> Upgraded our Web Service to use CXF 1.5.5 and our existing AXIS2 clients fail
> out with message
> - The given SOAPAction
> http://text2idml.idml.server.cequint.com/Text2IDMLWebServiceImpl/queryHandsets
> 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 http://cxf.apache.org/cve-2012-3451.html)
> 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 AXIX 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: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
