[
https://issues.apache.org/jira/browse/CAMEL-3438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972561#action_12972561
]
Claus Ibsen commented on CAMEL-3438:
------------------------------------
Sorry but we cannot accept the patch as it's tied to Spring. Its important the
camel-core is independent on any other framework.
Also classloading should work with OSGi, J2EE app servers and whatnot, so its
not trivial to do.
That said CamelContext has a classResolver which is runtime agnostic. So I
suggest to use that.
> 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.
