camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nick Heudecker (JIRA)" <j...@apache.org>
Subject [jira] Updated: (CAMEL-3438) JAXBDataFormatter should using Spring ApplicationContext's classLoader explicitly
Date Wed, 02 Feb 2011 00:48:29 GMT

     [ https://issues.apache.org/jira/browse/CAMEL-3438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Nick Heudecker updated CAMEL-3438:
----------------------------------

    Attachment: JaxbDataFormat.patch.diff

Attaching a patch to fix JaxbDataFormat when a JAXBContext is passed in instead of a context
path.  In the 2.6.0 version, the passed in JAXBContext is clobbered by the created context.
 

> 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
>          Components: camel-jaxb
>    Affects Versions: 2.4.0
>            Reporter: ext2
>            Assignee: Hadrian Zbarcea
>             Fix For: 2.6.0
>
>         Attachments: JaxbDataFormat.java, JaxbDataFormat.patch.diff
>
>
> 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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message