@Willem The payload is a simple JAXB annotated Pojo (In this case a Status message, containing some strings and maps).
To recap: 1. Unit tests (and actual operation) run fine without maven dependency of camel-jaxb. 2. Jaxb itself runs fine on the classes. Schema is generated and unit tests pass for marshalling. 3. Jaxb has not been 'activated' for the route. It's as simple as from(jms..).to(bean...). 4. The reason why I added Jaxb annotations to the working model is to eventually migrate to XML payload on the wire so we can integrate .NET clients. I feel simple inclusion of the camel-jaxb dependency should not alter the behavior of the code without explicit configuration. I am not sure why a FallbackTypeConfigurator would kick in if regular serialization works just fine without the dependency. -- View this message in context: http://camel.465427.n5.nabble.com/JAXB-causing-Unit-Test-Failure-without-any-actual-marshalling-active-tp3278807p3280121.html Sent from the Camel - Users mailing list archive at Nabble.com.
