You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Rich Scheuerle (JIRA)" <ji...@apache.org> on 2009/06/17 20:34:07 UTC

[jira] Resolved: (AXIS2-4392) JAXWS: Dispatch and Provider don't honor SOAPAction MIMEHeader

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

Rich Scheuerle resolved AXIS2-4392.
-----------------------------------

    Resolution: Fixed

Committed 785750

> JAXWS: Dispatch<SOAPMessage> and Provider<SOAPMessage> don't honor SOAPAction MIMEHeader
> ----------------------------------------------------------------------------------------
>
>                 Key: AXIS2-4392
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4392
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: jaxws
>            Reporter: Rich Scheuerle
>            Assignee: Rich Scheuerle
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> Scenario:
> A customer can use  Dispatch<SOAPMessage> or Provider<SOAPMessage> apis to interact with a web service at the SAAJ SOAPMessage level.
> The SAAJ SOAPMessage api allows the customer to set the transport MIME Headers for the message.
> If a customer sets the SOAPAction header using SAAJ, it is not being honored.
> Solution:
> The solution is to copy the value of the SOAPAction header onto the Axis2 MessageContext.
> This solution is provided by Wendy Rashke.  I am working with Wendy to commit the code.

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