synapse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Isuru Udana Loku Narangoda (JIRA)" <>
Subject [jira] [Created] (SYNAPSE-977) Issue with Header mediator with complex headers
Date Tue, 17 Sep 2013 18:24:55 GMT
Isuru Udana Loku Narangoda created SYNAPSE-977:

             Summary: Issue with Header mediator with complex headers
                 Key: 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

<definitions xmlns="">
   <proxy name="HeaderAndEnrichTest"
          transports="https http"
            <property name="HEADER_PROP" value="foo" scope="default" type="STRING"/>
            <header scope="default">
               <m:complexHeader xmlns:m="http://org.synapse.example">TEST</m:complexHeader>
            <switch xmlns:ns="http://org.apache.synapse/xsd"
               <case regex="MSFT">
                     <source type="property" clone="true" property="HEADER_PROP"/>
                     <target xmlns:m="http://org.synapse.example" xpath="$header/m:complexHeader"/>
                  <address uri="http://localhost:9000/services/SimpleStockQuoteService"/>

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:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message