Scott, Cheers that makes perfect sense, however I wanted to test was the actual errorHandler part from first post. I'll use the otherwise to handle incorrect headers but I want to maintain the errorHandler for unforeseen problems. I was wondering if there is a way to force a message to hit the error handler without bypassing my default config (i.e. without writing directly to the DLQ) just to check I have the error handler setup correctly in the routeBuilder.
Cheers, James. -- View this message in context: http://camel.465427.n5.nabble.com/Dead-letter-queue-when-header-not-matched-tp5723462p5723468.html Sent from the Camel - Users mailing list archive at Nabble.com.
