The above code works. It results in the route being rollbacked. The message
is kept on the queue, and our bundle is stopped.
Though what we don't understand is the position and roll of the
markRollbackOnly().
We expected to use this. But putting the markRollbackOnly after the
onException(IOExce
Okay we have got it working:
Transaction configuration:
Sample Route with onException:
Note: make the camel route BundleContextAware (by implementing
BundleContextAware)
//act upon th
Hai Claus,
Thanks for your reply.
Yes removing handled(true) makes sure that the transaction is rolledBack and
the message is kept on the queue. Thanks!
The route also stops working though we prefer the feature to be uninstalled
from Karaf (OSGI).
We are looking into getting the BundleContext
s stopped though we expected the message not to be dequeue'd but
it is dequeue'd.
Does anyone know how to achieve this?
Cheers,
Praan
--
View this message in context:
http://camel.465427.n5.nabble.com/Transactions-Error-Stop-route-tp5723438.html
Sent from the Camel - Users mailing list archive at Nabble.com.