[
https://issues.apache.org/jira/browse/CAMEL-3438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972916#action_12972916
]
ext2 commented on CAMEL-3438:
-----------------------------
Thanks for thequickly patch;
Just as Claus Ibsen has said, there are still other tweaks in OSGI.
The end user must make ensure that the generated JAXB class is visible to the
camel route's bundle;
some times the end-user should manually import the generated JAXB package , if
the generated JAXB class doesn't exists in the sample bundle of camel routes;
because the maven-bundle-plugin cannot recognize the spring configuration
automatically.
> JAXBDataFormatter should using Spring ApplicationContext's classLoader
> explicitly
> ---------------------------------------------------------------------------------
>
> Key: CAMEL-3438
> URL: https://issues.apache.org/jira/browse/CAMEL-3438
> Project: Camel
> Issue Type: Bug
> Affects Versions: 2.4.0
> Reporter: ext2
> Attachments: JaxbDataFormat.java
>
>
> JAXBDataFormatter now using JAXBContext.newInstance(path) to create
> JAXBContext,
> but this will using Thread's context classLoader.
> this may causing un-expected class or resource not found exceptions;
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
