Hi This one is being discussed at: http://fusesource.com/forums/thread.jspa?threadID=1167&tstart=0
On Thu, Aug 20, 2009 at 9:36 PM, thabach<[email protected]> wrote: > > Heya > > I am implementing a staged architecture with SedaEndpoints and have a > question on producer semantics. > > To my surprise I realized that once the queue gets full an > IllegalStateException is thrown and with the Camel 2.0 default error > handling semantics, my Exchange object gets essentially "lost". So here come > my questions : > > * Why does the SedaProducer call add() on its BlockingQueue and not put() ? > There are probably good reasons and I am interested :confused:. > > * What is the best practice / pattern in implementing put() semantics ? > > * Why does my original caller not get the exception ? My route has a source > endpoint connected to a router connected to the SedaEndpoint and I was > expecting the source endpoint to get the IllegalStateException wrapped in a > RuntimeCamelException (as described > http://camel.apache.org/error-handling-in-camel.html) or shouldn't it ? > > Thanks for your clarifications and advice, Christian. > -- > View this message in context: > http://www.nabble.com/SedaProducer-Questions-tp25068491p25068491.html > Sent from the Camel - Users mailing list archive at Nabble.com. > > -- Claus Ibsen Apache Camel Committer Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus
