Mario, it sounds like those properties are really part of the logic. Why not keep it next to the data then? Wrap your payload in some envelope with business properties stored in it.
HTH,
Andrew
On Jul 2, 2009 8:50 AM, "Mario Klaver" <mule.user.relay@...> wrote:
Andrew,
This only works with synchronous endpoints, right? I'm using an asynchronous model and was wondering how to pass properties from service to service (or endpoint to endpoint ;-) ). For example in the first step I indicate certain messages as test messages. When a test message arrives at my LogComponent, I don't want it to be logged (because it is a test message). I'm using the MuleMessage properties to store this information, but with some routers the properties are lost (for example the chaining-router). I fixed this by extending the chaining-router. In the processIntermediaryResult method the properties of the intermediary MuleMessage are copied to the local MuleMessage. But to extend routers for this functionality is not desirable. Is there another way to achieve this (besides altering the payload and storing it there?)
I tried the MuleSession but the Session object in my first step is different than the Session object at my LogComponent.
Regards,
Mario
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
