Hi,
I have the following configuration:
errorHandler(
deadLetterChannel("direct:deadChannel")
.disableRedelivery()
);
from("direct:inbox")
.enrich("direct:enri
Hi,
As best I can tell, there is just one error handler for the entire context.
Is there a way to create a custom error handler that can be applied
around a single endpoint?
~ Greg McFall
I just tried it. Sadly, the inOnly() trick does not work.
On Fri, May 27, 2011 at 5:50 PM, Donald Whytock wrote:
> Have you tried using inOnly()? As in
>
> from(start).loop(3).inOnly().to(endpoint);
>
> On Fri, May 27, 2011 at 5:34 PM, Greg McFall
> wrote:
> > Don,
;d want to modify the
> same exchange over and over. So the functionality of the loop is
> entirely dependent on the functionality of the processor you attach to
> it.
>
> On Fri, May 27, 2011 at 4:48 PM, Greg McFall
> wrote:
> > Don,
> >
> > Yes, that mig
ange.copy()); }
>
> }
>
> Then use it in your loop:
>
> from(endpoint)
>.process(new LoopProcessor(new CopyProcessor(processor)));
>
> On Fri, May 27, 2011 at 1:24 PM, Greg McFall
> wrote:
> > Don,
> >
> > I don't understand what you are p
doesn't get
> changed?
>
> Don
>
> On Fri, May 27, 2011 at 12:36 PM, Greg McFall
> wrote:
> > Hi,
> >
> > The Camel documentation contains the following statement about the Loop
> > pattern:
> >
> > The Loop allows to process a messag
iteration?
Cheers,
Greg McFall
gt; > return body + "." + count;
> > }
> > }
> >
> > @Override
> > protected RouteBuilder createRouteBuilder() {
> > return new RouteBuilder() {
> >
> > @Override
> > public void configure() throws Exception {
> > err
eliveries(3)
.redeliveryDelay(500)
);
MyService bean = new MyService();
from("direct:inbox")
.bean(bean, "enrich")
.to("mock:sink");
}
};
}
}
Thanks,
~ Greg McFall
