We disable by default, but ship every example with the DLQ explicitly configured to be amq.. so that way when folks copy examples they get the dlq behavior, but at least it's explicit and in their face.
On Mon, Jun 23, 2008 at 6:52 AM, James Strachan <[EMAIL PROTECTED]> wrote: > 2008/6/23 Gert Vanthienen <[EMAIL PROTECTED]>: >> James, >> >> This would be a good solution for people using Camel with ActiveMQ (and >> possibly also for ServiceMix), but isn't Camel supposed to be more >> transport/technology-agnostic? If Camel is also intended to be used as a >> mediation/routing engine for CXF, MINA, ..., I don't think there is a >> single, non-sucky default error handler configuration for all those. > > I hear you - but I kinda was thinking, even if folks were using CXF or > MINA and not ActiveMQ then at least the default would fail (and act > kinda like no error handler?) > > >> Would >> it be an option to have no default error handler inside Camel, but let the >> underlying system add something non-sucky (with a big WARN message) >> implicitly whenever a good default for that system exists and no error >> handler was set in the RouteBuilder itself? > > I guess we could see if there is ActiveMQ available, then default the > error handler to DLQ using that; otherwise don't add an error handler? > > -- > James > ------- > http://macstrac.blogspot.com/ > > Open Source Integration > http://open.iona.com > -- Regards, Hiram Blog: http://hiramchirino.com Open Source SOA http://open.iona.com
