Now I remember what I perceived an issue with static routing slip. We have to call 2 InOnlyMEP endpoints in a sequence.
Call x FTPSender endpoint->Call y FTPSender endpoint I think static routing slip only supports In-Out MEP. Please correct me if I am wrong.. Regards, Rabi Mishra ________________________________ From: Bruce Snyder [mailto:[EMAIL PROTECTED] Sent: Tue 4/8/2008 9:54 PM To: [email protected] Subject: Re: Transaction in a Bean SU On Tue, Apr 8, 2008 at 6:14 PM, <[EMAIL PROTECTED]> wrote: > There no error. The problem I am having is.. all calls to all previous > endpoints succeed inspite of error in call to one subsequent endpoint. I want > them to be rolled back aswell. > > This bean is a target to file poller. So the file is not deleted (which > should be the case if there is an error). But, some of the jdbc and camel > persist calls succeed... > > I test this by dropping one of the db objects used.. Could you please outline the flow through the components for me so I can better understand what you're doing? I'm asking this partially because I'm wondering about suggesting that you make use of a static routing slip instead of trying to use the servicemix-bean component as a generic router. Bruce -- perl -e 'print unpack("u30","D0G)[EMAIL PROTECTED]&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*" );' Apache ActiveMQ - http://activemq.org/ Apache Camel - http://activemq.org/camel/ Apache ServiceMix - http://servicemix.org/ Apache Geronimo - http://geronimo.apache.org/ Blog: http://bruceblog.org/ The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com
