« Return to Thread: MuleMessage properties during all journey through synchronous endpoints

Re: MuleMessage properties during all journey through synchronous endpoints

by Andrew Perepelytsya :: Rate this Message:

Reply to Author | View in Thread

Anatoli,

I assume you're using recent Mule release (2.2.1?). Message properties are actually scoped, thus inbound properties will not end up in response scope. From your description it looks like you need a correlation to be preserved. So, granted the remote system doesn't drop your custom properties, take a look at <expression-message-info-mapping/>, it let's you customize what properties are used for correlation, how to extract them from a message, and where to get a match from the response message.

HTH,
Andrew

On Tue, Jun 30, 2009 at 12:12 PM, Anatoli Kuzmin <anatoli.kuzmin@...> wrote:
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

 « Return to Thread: MuleMessage properties during all journey through synchronous endpoints