On Thu, Apr 5, 2012 at 8:44 PM, Abid Khan <[email protected]> wrote:
> I think we need to develop another mediator that is like filter mediator; > but the condition is send success or send failed, and can invoke another > sequence or set of mediators in both cases (i.e. send succeeded or failed). > Kind of branching of the sequence based on the send success or failure. > This is already supported with the callout mediator (blocking send). If successful the following mediators will execute. Otherwise the fault sequence will execute. Thanks, Hiranya > > Regards, > Abid > > > > -----Original Message----- > From: Hiranya Jayathilaka [mailto:[email protected]] > Sent: Thursday, April 05, 2012 7:19 AM > To: [email protected] > Subject: Re: SEND mediator > > Hi Paul, > > On Thu, Apr 5, 2012 at 2:06 PM, Paul Fremantle <[email protected]> wrote: > > > Hiranya > > > > I agree this is one way, but its a little complex. Maybe we should add a > > JIRA to try and come up with a simpler solution? > > > > I'm sorry but I didn't get your point. Do you mean that the way we handle > out-only sends is too complex? Or do you mean that the error handling > mechanism for out-only messages is too complex? I believe a comm error in > an out-only message will trigger the respective fault sequences and the > usual error handling logic of Synapse will kick in. > > Thanks, > Hiranya > > > > > > Paul > > > > On Wed, Apr 4, 2012 at 4:53 AM, Hiranya Jayathilaka < > [email protected] > > >wrote: > > > > > On Wed, Apr 4, 2012 at 6:51 AM, Abid Khan <[email protected]> > > wrote: > > > > > > > I have a configuration where I am publishing some messages. > > > > > > > > In the configuration I have set the property to OUT_ONLY to be true. > > > > > > > > But still I want to know if the message was posted or received by the > > > > other application, which mean is there anything in the MesageContext > > that > > > > tells me that the message was posted successfully? > > > > > > > > > > Such a communication error would usually result in an endpoint error > and > > > the endpoint would be forced into either the TIMEOUT state or the > > SUSPENDED > > > state. > > > > > > Thanks, > > > Hiranya > > > > > > > > > > > > > > Regards, > > > > > > > > Abid > > > > > > > > > > > > > > > > -- > > > Hiranya Jayathilaka > > > Associate Technical Lead; > > > WSO2 Inc.; http://wso2.org > > > E-mail: [email protected]; Mobile: +94 77 633 3491 > > > Blog: http://techfeast-hiranya.blogspot.com > > > > > > > > > > > -- > > Paul Fremantle > > Co-Founder and CTO, WSO2 > > Apache Synapse PMC Chair > > OASIS WS-RX TC Co-chair > > > > blog: http://pzf.fremantle.org > > [email protected] > > > > "Oxygenating the Web Service Platform", www.wso2.com > > > > > > -- > Hiranya Jayathilaka > Associate Technical Lead; > WSO2 Inc.; http://wso2.org > E-mail: [email protected]; Mobile: +94 77 633 3491 > Blog: http://techfeast-hiranya.blogspot.com > -- Hiranya Jayathilaka Associate Technical Lead; WSO2 Inc.; http://wso2.org E-mail: [email protected]; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com
