Hi Claus, Unfortunately, this issue reproduces with the last 2.2-SNAPSHOTS artifacts from the apache.snapshots repo... I managed to workaround it the way I previously explained : - routing the multicast bean to a "direct:webservices" channel, - wiring "direct:webservices" and "direct:webservices-with-deadletterchannel" channels with a RouteBuilder defining a dead letter channel - my content-based router consumes the "direct:webservices-with-deadletterchannel", and drives the messages along the webservices
That's not clean, I am not satisfied with this, but this works for the moment. But the risk here of loosing messages is higher, isn't it ? Could the use of a transactional error handling bring something here with the direct channels ? -- Olivier Claus Ibsen-2 wrote: > > On Thu, Feb 4, 2010 at 11:02 PM, Olivier Billard > <olivier.bill...@gmail.com> wrote: >> >> Yep, sorry, I am using the latest stable release : 2.1.0. >> > > Can you try 2.2-SNAPSHOT or wait till 2.2 is released. > http://camel.apache.org/download.html > > I think we fixed an issue with setting error handler ref on camel context. > > -- > Claus Ibsen > Apache Camel Committer > > Author of Camel in Action: http://www.manning.com/ibsen/ > Open Source Integration: http://fusesource.com > Blog: http://davsclaus.blogspot.com/ > Twitter: http://twitter.com/davsclaus > > ----- -- Olivier Billard -- View this message in context: http://old.nabble.com/Defining-a-DeadLetterChannel-when-using-POJO-annotations-tp27455914p27465224.html Sent from the Camel - Users mailing list archive at Nabble.com.
