[ 
https://issues.apache.org/jira/browse/AXIS2-5480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13569795#comment-13569795
 ] 

Hudson commented on AXIS2-5480:
-------------------------------

Integrated in Axis2 #2204 (See [https://builds.apache.org/job/Axis2/2204/])
    Applied patch for AXIS2-5480 (Revision 1441907)

     Result = SUCCESS
sagara : 
Files : 
* 
/axis/axis2/java/core/trunk/modules/kernel/src/org/apache/axis2/engine/DefaultObjectSupplier.java

                
> SOAPAction being set even when WSDL has soapAction=""
> -----------------------------------------------------
>
>                 Key: AXIS2-5480
>                 URL: https://issues.apache.org/jira/browse/AXIS2-5480
>             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 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". 

--
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]

Reply via email to