I am sorry Supun, I do not quite get what you try to say, (I know it might be hard to explain) may be a patch would explain it, if it is not much work.
Thanks, Ruwan On Wed, Dec 1, 2010 at 12:14 PM, Supun Kamburugamuva <[email protected]>wrote: > The way errors are handled in the SynapseCallbackReceiver is pretty strange > to me. When an error happens at the transport sender this callback receiver > is invoked. But when it is invoked, it uses the incoming message context to > invoke the synapse configuration and send back the message. But there is a > message context originated from the transport itself. Synapse callback > doesn't use this message context for invoking the language. > > This makes the life hard at the handling of faults in Synapse > configuration. To send the fault back to the user, user has to do things > like removing the To address and setting the RESPONSE to true. > > I would like to re-factor this code to use the original message context > coming from the transport. WDYT? > > Thanks, > Supun.. > > -- Ruwan Linton Software Architect & Product Manager, WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org Lean . Enterprise . Middleware phone: +1 408 754 7388 ext 51789 email: [email protected]; cell: +94 77 341 3097 blog: http://blog.ruwan.org linkedin: http://www.linkedin.com/in/ruwanlinton google: http://www.google.com/profiles/ruwan.linton tweet: http://twitter.com/ruwanlinton
