karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Baptiste Onofré (Resolved) (JIRA) <j...@apache.org>
Subject [jira] [Resolved] (KARAF-838) Simplify the way classloading works in Cellar
Date Thu, 26 Jan 2012 16:06:39 GMT

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

Jean-Baptiste Onofré resolved KARAF-838.

    Resolution: Fixed
> Simplify the way classloading works in Cellar
> ---------------------------------------------
>                 Key: KARAF-838
>                 URL: https://issues.apache.org/jira/browse/KARAF-838
>             Project: Karaf
>          Issue Type: Improvement
>          Components: cellar-core
>    Affects Versions: cellar-2.2.2, cellar-2.2.1
>            Reporter: Ioannis Canellos
>            Assignee: Jean-Baptiste Onofré
>             Fix For: cellar-3.0.0, cellar-2.2.3
> Hazelcast (which is used by cellar) relies on the Thread Context ClassLoader (tccl) in
order to serialize and deserialize objects that are being exchanged between nodes.
> Cellar currently, sets the bundle class loader to the thread context classloader in order
to have objects serialized and deserialized, which is not that bad (as lots of frameworks
do so). 
> When a user builds an application that reuses the Cellar ClusterManager service, will
have to do the same. I would like to find a way to avoid that. 

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


View raw message