Nick, I have created a JIRA for this [1].
I will look in to this in detail and fix the issue, so that you can use your old SynEnv.createMessageContext to get this done. Give me some time to clean it up and fix this. Thanks for pointing this. Thanks, Ruwan. On 7/12/07, Nick Cook <[EMAIL PROTECTED]> wrote:
On 12 Jul 2007, at 04:06, Ruwan Linton wrote: >> >> - well the first problem was that the original message associated >> with the mediator's original "ctx" got overwritten by the new message >> (because they shared the same context). I solved this by storing the >> original envelope, action, to endpoint etc. and writing them back >> into "ctx" when I'd sent the new message. So far so good, but then I >> got the following exception: > > > Haven't you tried to clone the message? I think that will solve > this problem > (but not that sure) - I could have but the main problem isn't creating the new message to send. As you say, it is the sharing of transport headers. Presumably, synapse (or Axis2 underneath) does not see the new message as being in a genuinely different context. Or at least that's my interpretation. Nick --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Ruwan Linton http://www.wso2.org - "Oxygenating the Web Services Platform"
