So if I have the following:
from("direct:a").split(...).streaming().bean(myBean)
where myBean uses a producer template to send to direct:b when part of the
stream is processed (we had to use this instead of an aggregator)
from("direct:b).bean(myOtherBean) ...
Say something went wrong in myOtherBean (an exception was raised). What
would be a way to tell direct:a to stop?
On Thu, Aug 29, 2013 at 8:27 PM, Christopher Gardner <
[email protected]> wrote:
> I'm using stoponexception. My splitter route includes a bean processor
> that uses producer template to push to the downstream route, which isn't a
> JMS route. Would you show a bit of DSL that might work on my downstream
> route that could signal my upstream route an exception occurred?
> On Aug 29, 2013 7:59 PM, "Raul Kripalani" <[email protected]> wrote:
>
>> Have you tried the stopOnException() option of the Splitter?
>> Use it in combination with direct or seda endpoints. If you use JMS, you
>> can enable the transferException option to ensure that the Exception is
>> propagated back to the caller in its original form.
>>
>> Regards,
>>
>> *Raúl Kripalani*
>> Apache Camel PMC Member & Committer | Enterprise Architect, Open Source
>> Integration specialist
>> http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
>> http://blog.raulkr.net | twitter: @raulvk
>>
>> On Thu, Aug 29, 2013 at 11:58 PM, Christopher Gardner <
>> [email protected]> wrote:
>>
>> > I have a number of routes that do a bit of processing and then hand off
>> to
>> > other routes. One of the upstream routes splits streaming data to a
>> > downstream route. If that downstream route encounters problems it
>> should
>> > notify the upstream route to stop splitting and cease processing. What
>> > mechanisms does camel provide to help?
>> >
>>
>
