Claus Ibsen-2 wrote > > On Wed, May 30, 2012 at 2:09 PM, Jens wrote: >> >> Jens wrote >>> >>> >>> Claus Ibsen-2 wrote >>>> >>>> Hi >>>> >>>> Have you tried enabling stream caching? >>>> http://camel.apache.org/stream-caching.html >>>> >>> >>> Yes, and I also tried converting the message to a String right away but >>> neither change helped. >>> >>> This is with Camel 2.8.3, by the way. >>> >> >> It seems this problem is in some way related to the CXF component. If I >> simply replace the routing to the primary CXF endpoint with a >> throwException >> the route works as expected, resuming with the original message in the >> catch >> block. So does the CXF component "erase" the orignal message? Is this >> worthy >> of filing a bug? >> > > Yes it would help a lot if you can create a small sample application / > unit test that reproduces the issue. > And then create a JIRA ticket and attach the sample.\ >
https://issues.apache.org/jira/browse/CAMEL-5356 -- View this message in context: http://camel.465427.n5.nabble.com/doTry-doCatch-with-original-message-tp5713695p5714289.html Sent from the Camel - Users mailing list archive at Nabble.com.
