[ 
https://issues.apache.org/jira/browse/AXIS2-3943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Isuru Eranga Suriarachchi resolved AXIS2-3943.
----------------------------------------------

       Resolution: Fixed
    Fix Version/s: 1.6

Resolving the issue as the commit which caused the test failure has already 
been reverted..

> server outbound message populated with incorrect HTTP SOAP Action header
> ------------------------------------------------------------------------
>
>                 Key: AXIS2-3943
>                 URL: https://issues.apache.org/jira/browse/AXIS2-3943
>             Project: Axis2
>          Issue Type: Bug
>          Components: jaxws
>            Reporter: Mike Rheinheimer
>             Fix For: 1.6
>
>
> Recently, Deepal made a change to 
> org.apache.axis2.description.AxisOperation.getSoapAction() in SVN rev 670462 
> to call getInputAction() instead of return soapAction:
> http://svn.apache.org/viewvc/webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/description/AxisOperation.java?r1=645181&r2=670462
> The latest CTS run has a server side inbound handler that shows a failure:
> 194932 [7/23/08 9:57:31:662 CDT] 0000002e SystemOut     O   result=FAILED: 
> unex
> pected value found in HTTP 
> SOAPAction:[["http://w2jrlr2745testservice.org/W2JRLR
> 2745TestService.wsdl/W2JRLR2745TestOne/echoStringResponse"]]
> So, I think this means that the client is populating the message with an 
> incorrect soap action header, due to the above mentioned change. 
> I would guess there are two possible fixes:
> 1)  make getSoapAction method "direction aware" so it can call 
> getInputAction() or getOutputAction() as appropriate
> 2)  revert the change in 670462 
> Deepal, your opinion?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to