Thanks for following up. In the meantime I have moved on and created a custom Processor chained into the route, which provides more flexibility for other processing.
The rest of the stack trace just went further into the jaxb RI and didn't seem to provide additional clues why Camel is picking this up. The routes are simple from(bean).to(jms) and reverse. My theory is still that some Camel component is latching on to JAXB annotated payload without explicit configuration but we are too time constrained to dig into it. -- View this message in context: http://camel.465427.n5.nabble.com/JAXB-causing-Unit-Test-Failure-without-any-actual-marshalling-active-tp3278807p3279154.html Sent from the Camel - Users mailing list archive at Nabble.com.
