
Some parts of this message have been removed.
Learn more about Nabble's
security policy.
I think it depends on what the transport
is doing. Many transports and components will strip properties from the
MuleMessage during transactions. For what you are trying to do, I suggest you
use the MuleRegistry. That’s what I do to track properties that I want to use between
multiple endpoints (and that’s what its intention is). You usually need to use
your own component to get to the MuleRegistry as it can only be obtained
through the MuleContext. Take a look at
http://www.mulesource.org/display/MULE2USER/Storing+Objects+in+the+Registry
Neil
From: Anatoli Kuzmin
[mailto:anatoli.kuzmin@...]
Sent: Tuesday, June 30, 2009 12:13
PM
To: user@...
Subject: [mule-user] MuleMessage
properties during all journey through synchronous endpoints
Hi
Can my message save custom properties if I use synchronous endpoints during all
journey?
I want to set custom properties in the first transformer T1 (using
message.setStringProperty("SessionID",ctSession);)
and get it in responseTransformer T2.
Unfortunately message had have the same unique id but my custom properties was
lost.
Also I tried to set correlationId - the same.
<http:endpoint name="clientEndpoint" address="http://localhost:4019
" synchronous="true"/>
<http:endpoint name="serverEndpoint"
address="http://localhost:4020"
synchronous="true"/>
<custom-transformer class="Trans1"
name="T1"/>
<custom-transformer class="Trans2"
name="T2"/>
<model name="main">
<service
name="HttpProxyService">
<inbound>
<inbound-endpoint ref="clientEndpoint" />
</inbound>
<outbound>
<pass-through-router>
<outbound-endpoint ref="serverEndpoint"
transformer-refs="T1"
responseTransformer-refs="T2">
</outbound-endpoint>
</pass-through-router>
</outbound>
</service>
--
Best regards,
Anatoli Kuzmin