Hi all,
just tried out to instantiate a CustomProcessor in a route (like it is
documented)
But this does not work.
Error: Cannot resolve method 'process(Class)'
Should we remove this from documentation?
USING A PROCESSOR IN A ROUTE
Once you have written a class which implements processor like th
Hi
Yeah you should create an instance
from("activemq:myQueue").process(new MyProcessor());
On Thu, Sep 22, 2022 at 2:35 PM Michael Rambichler
wrote:
> Hi all,
>
> just tried out to instantiate a CustomProcessor in a route (like it is
> documented)
> But this does not work.
> Error: Cannot re
Dear Mr/Mrs,
I'm trying to use doTry, doCatch, and doFinally for ToD as shown in the
screenshot.
However, the error was thrown inside the "sub-route" called in ToD and it was
not catch by DoCatch.
May I know if there is any other way to catch error while calling ToD, and
ignore the exception?
Hi
There is no screenshot in this email.
But if you call a sub route then it has its own error handler, so you need
to turn this off for the route to let it work with your doTry .. doCatch.
Or avoid calling a sub route.
On Thu, Sep 22, 2022 at 3:37 PM Brian Lee wrote:
> Dear Mr/Mrs,
>
> I'm try
On 2022/09/07 07:42:52 Simo Hakanen wrote:
> Hello list
>
> We use camel to route messages over sjms (activemq) between processes,
> where the remote end runs a route that does some processing and returns a
> large json-response.
> After experimenting with streamcaching on that remote end, we notic
