-
Bug
-
Resolution: Done
-
Major
-
None
-
1.6.1.0-fuse
-
None
-
None
When a Camel route consuming from jbi endpoint tries to use camel-jaxb to unmarshal incoming xml data causes jaxb exception. The same route if changed to file poller (in place of jbi) works without any problem.
I have attached a test to reproduce the problem here.
To run the test
1. do mvn install in top level directory.
2, copy bridge-camel-sa/target/bridge-camel-sa-4.1.0.2-fuse.zip and rider-auto-example/target/rider-auto-example-1.0.jar
to FUSE ESB 4.1.0.2 deploy directory. (you may need to manually start camel-jms and camel-jaxb bundles with features/install)
3. run mvn exec:java inside client directory.
If you run tail on servicemix log or do log d in console you can see JAXB exception.
Caused by: javax.xml.bind.JAXBException: "org.fusesource.camel" doesnt contain ObjectFactory.class or jaxb.index
at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:183)
If you look at the bundle jaxb.index file is already present and the route if changed to file poller works without any problem.