I've been expermenting with camel 1.6.1, and come across a problem/bug with
OnException.
With the following route (greatly simplified for testing) everything works
as expected and a file put into input shows up into output, and nothing
shows up in the exception directory:
<route>
<from uri="file:///c:/temp/input"></from>
<onException>
<exception>java.lang.Exception</exception>
<handled><constant>true</constant></handled>
<to uri="file:///c:/temp/exception">
</onException>
<to uri="file:///c:/temp/output"></to>
</route>
However, when I have OnExceptions inside of multicast, things don't quite
work as expected, the input
file ends up in output & output2 as expected, but it also ends up in the
exception and exception2 directorys, which shouldn't happen, since no
exception is thrown in the route :
<route>
<from uri="file:///c:/temp/input"></from>
<multicast>
<pipeline>
<onException>
<exception>java.lang.Exception</exception>
<handled><constant>true</constant></handled>
<to uri="file:///c:/temp/exception">
</onException>
<to uri="file:///c:/temp/output"></to>
</pipeline>
<pipeline>
<onException>
<exception>java.lang.Exception</exception>
<handled><constant>true</constant></handled>
<to uri="file:///c:/temp/exception2">
</onException>
<to uri="file:///c:/temp/output2"></to>
</pipeline>
</multicast>
</route>
Three possibilites come to mind:
1. I've got something wrong in the route
2. It's a bug in multicasting/onexception
3. I'm just not understanding something correctly.
Any help would be appreciated.
--
View this message in context:
http://www.nabble.com/Multicast---OnException----Bug--%28camel-1.6.1%29-tp25028431p25028431.html
Sent from the Camel - Users mailing list archive at Nabble.com.
