camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From enalposi <>
Subject Re: JAXB causing Unit Test Failure without any actual marshalling active
Date Thu, 25 Nov 2010 14:22:03 GMT


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
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
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

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:
Sent from the Camel - Users mailing list archive at

View raw message