Isuru Udana Loku Narangoda created SYNAPSE-977:
--------------------------------------------------
Summary: Issue with Header mediator with complex headers
Key: SYNAPSE-977
URL: https://issues.apache.org/jira/browse/SYNAPSE-977
Project: Synapse
Issue Type: Bug
Affects Versions: 3.0
Reporter: Isuru Udana Loku Narangoda
Assignee: Hiranya Jayathilaka
In the following configuration, if the message goes through the case path,
complex header value is changed using the enrich mediator.
At the same time header mediator value is also getting changed.
So after one request goes through the case path, any other subsequent messages
will also get the header value set by the enrich mediator even they are not
dispatched through the case path.
<definitions xmlns="http://ws.apache.org/ns/synapse";>
<proxy name="HeaderAndEnrichTest"
transports="https http"
startOnLoad="true"
trace="disable">
<description/>
<target>
<inSequence>
<property name="HEADER_PROP" value="foo" scope="default"
type="STRING"/>
<header scope="default">
<m:complexHeader
xmlns:m="http://org.synapse.example";>TEST</m:complexHeader>
</header>
<switch xmlns:ns="http://org.apache.synapse/xsd";
xmlns:m0="http://services.samples";
source="//m0:symbol">
<case regex="MSFT">
<enrich>
<source type="property" clone="true"
property="HEADER_PROP"/>
<target xmlns:m="http://org.synapse.example";
xpath="$header/m:complexHeader"/>
</enrich>
</case>
<default/>
</switch>
<send>
<endpoint>
<address
uri="http://localhost:9000/services/SimpleStockQuoteService"/>
</endpoint>
</send>
</inSequence>
</target>
</proxy>
</definitions>
--
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]
