[KARAF-838] Simplify the way classloading works in Cellar

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: cellar-2.2.2, cellar-2.2.1
• Fix Version/s: cellar-3.0.0, cellar-2.2.4
• Component/s: cellar
• Assignee: Jean-Baptiste Onofré
• Reporter: Ioannis Canellos
• Created: 27/Aug/11 11:23
• Updated: 13/Sep/18 13:07
• Resolved: 26/Jan/12 16:06

Description

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.