[AXIS2-5480] SOAPAction being set even when WSDL has soapAction=""

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.6.2
• Component/s: wsdl
• Assignee: Unassigned
• Reporter: Wayne Holmes
• Created: 30/Jan/13 17:10
• Updated: 03/Feb/13 15:17

Description

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 AXIS generated stubs causing problems with server upgrade to CXF 1.5.5 from CXF 1.5.0".