camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CAMEL-4915) Serialisation Data Format is unable to unmarshal in OSGi environment
Date Thu, 19 Jan 2012 10:52:40 GMT

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

Claus Ibsen updated CAMEL-4915:
-------------------------------

    Priority: Minor  (was: Major)
    
> Serialisation Data Format is unable to unmarshal in OSGi environment
> --------------------------------------------------------------------
>
>                 Key: CAMEL-4915
>                 URL: https://issues.apache.org/jira/browse/CAMEL-4915
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 2.9.0
>         Environment: Karaf 2.2.0 with Equinox 3.6.0.v20100517
>            Reporter: Raul Kripalani
>            Assignee: Claus Ibsen
>            Priority: Minor
>              Labels: serialization
>             Fix For: 2.9.1, 2.10.0
>
>
> This happens because camel-core doesn't have access to custom classes. Maybe this data
format should be isolated into it's own package and have DynamicImport-Package: * in its manifest
headers. That way it will be able to access any class from the environment.
> Another possibility is to dig deeper into what classloader is being used to resolve the
class. It seems like the camel-core classloader is used rather than the TCCL. Possible culprit
could be http://docs.oracle.com/javase/6/docs/api/java/io/ObjectInputStream.html#resolveClass(java.io.ObjectStreamClass).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message