[
https://issues.apache.org/jira/browse/SYNAPSE-64?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
indika priyantha kumara resolved SYNAPSE-64.
--------------------------------------------
Resolution: Fixed
Now synapse can get the transport headers, property from the Axis2
configuration Context using XPath function
synapse:get-property(scope,prop-name)
ex: To get SOAP header To synapse:get-property('transport','To')
Using the property mediator, setting and removing above properties are also
possible
ex:
To set the transport header
<property name="To" value="http://www.example.com" scope="transport" />
To remove the transport header
<property name="To" scope="transport" action="remove"/>
> Allow use of SOAP header elements or xpath extractions from the SOAP body to
> set HTTP request headers when delegating to POX services
> -------------------------------------------------------------------------------------------------------------------------------------
>
> Key: SYNAPSE-64
> URL: https://issues.apache.org/jira/browse/SYNAPSE-64
> Project: Synapse
> Issue Type: New Feature
> Reporter: Michael Griffin
> Assigned To: indika priyantha kumara
>
> When using a proxy to delegate back to a POX service it would be nice to
> allow for values from the incoming SOAP headers or to use an xpath expression
> to extract values to be used as HTTP request headers send to the delegate.
--
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]