You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "xuhongbo (JIRA)" <ji...@apache.org> on 2010/12/17 18:40:01 UTC

[jira] Issue Comment Edited: (CAMEL-3438) JAXBDataFormatter should using Spring ApplicationContext's classLoader explicitly

    [ https://issues.apache.org/jira/browse/CAMEL-3438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972556#action_12972556 ] 

xuhongbo edited comment on CAMEL-3438 at 12/17/10 12:39 PM:
------------------------------------------------------------

This is a patch for JAXBDataFormatter to explicitly using Spring Application context's class loader;

please check the JAXBDataFormatter .getContext() method

      was (Author: ext2xhb):
    This is a patch for JAXBDataFormatter to explicitly using Spring Application context's class loader;
  
> 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.