Hi all,
I'm writing a custom security mediator and I need to unique identify a
request-response flow within Synapse so as to store certain security data.
I had thought to use the messageID that offers the Synapse MessageContext but
I've found that:
A) At request phase the messageID is empty until it arrives to the send
mediator. At send moment the axis2 MessageContext is cloned and a random
messageID is generated for the new (cloned) message. (This occurs in
Axis2FlexibleMEPClient.cloneForSend)
B) At response phase the messageID is the generated on the previous point.
Due to that, mediators prior to the send mediator have no messageID (AFAIK),
then:
1. There's another id (of some form) that I can use for the purpose of unique
identify a request-response flow?
2. Why the messageId is not set as soon as Synapse mediation starts and use it
for the rest of the mediation?
Thanks all,
Jose
______________________________________________
¿Con Mascota por primera vez? Sé un mejor Amigo. Entra en Yahoo! Respuestas
http://es.answers.yahoo.com/info/welcome
