Pablo La Greca
2012-06-27 16:13:55 UTC
The xml file will be the payload of your message. There's no way mule can magically know that the content in header element should be an inbound property.
<br /><br />
What you should do is extract the value of the upstream element and set it in an invocation variable so you can use it later.
<br /><br />
Since mule 3.3:
<br />
<code>
<br />
<set-variable variableName="upstreamHeader" value="#[xpath(//events/upstream)]"/>
<br />
</code>
<br />
Before mule 3.3:
<br />
<code>
<br />
<message-properties-transformer scope="invocation">
<br />
<add-message-property key="upstreamHeader" value="#[xpath://events/upstream]"/>
<br />
</message-propertes-transformer>
<br />
</code>
<br />
HTH, Pablo.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
<br /><br />
What you should do is extract the value of the upstream element and set it in an invocation variable so you can use it later.
<br /><br />
Since mule 3.3:
<br />
<code>
<br />
<set-variable variableName="upstreamHeader" value="#[xpath(//events/upstream)]"/>
<br />
</code>
<br />
Before mule 3.3:
<br />
<code>
<br />
<message-properties-transformer scope="invocation">
<br />
<add-message-property key="upstreamHeader" value="#[xpath://events/upstream]"/>
<br />
</message-propertes-transformer>
<br />
</code>
<br />
HTH, Pablo.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email