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" <[email protected]
>:
> 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?
> > >
> >
>
