Hi,
is there a way to let Camel consume poisoned (unprocessable) messages? I
haven't had any luck so far.
My setup:
Apache Camel 1.6.0 on Spring 2.5.6 on JBoss AS 5.0.0
All Camel routes start and end in JMS queues, consuming and producing is
transacted (Spring-JtaTransactionManager)
Routes are s
On Sat, Apr 18, 2009 at 10:25 AM, Roman Kalukiewicz
wrote:
> Hello,
>
> Just a quick note here. People usually get confused by what happens in
> getOut() method. Sometimes people just want to check if out message
> simply exists and they call getOut(). What happens is out message
> being created t
Hello,
Just a quick note here. People usually get confused by what happens in
getOut() method. Sometimes people just want to check if out message
simply exists and they call getOut(). What happens is out message
being created that is not what usually happens with methods that
conform to JavaBeans