Use stopOnException and rethrow the exception from the producer template.
On Fri, Aug 30, 2013 at 11:39 AM, Christopher Gardner
wrote:
> 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
Why using a bean in your first route if you only call a direct endpoint?
Why not:
from()
.split().streaming()
.to("direct:sub");
Best,
Christian
Am 30.08.2013 02:28 schrieb "Christopher Gardner" :
> I'm using stoponexception. My splitter route includes a bean processor
> that uses produce
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 myOther
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, 201
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
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
mechanism
