[
https://issues.apache.org/jira/browse/CAMEL-3438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972843#action_12972843
]
Claus Ibsen commented on CAMEL-3438:
------------------------------------
I have modified JaxbDataFormat a bit more to let it leverage the
ApplicationContext classloader if it was present.
I also optimized and removed the need for synchronization to initialize various
pieces as we can do this in start now.
trunk: 1050688.
> 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: xuhongbo
> 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.
