Deserialization issues in CEP environment

Question

Hi,
I'm running Coherence in a CEP environment, though I'm not making use of the CEP API inside the Spring context. The cache is initialized in this most basic way:
CacheFactory.getCache(SomeAbstract.class);
It resides in bundleA, where SomeAbstractBase.class also is. There are several implementations of this base class across multiple bundles, and I would like to make use of Coherence to store these instances.
I was expecting deserialization issues so I figured this would work, but it doesn't. What am I doing wrong here? What is the best approach to do this?
    Map<Long, ClassLoader> classLoaderMap = new HashMap<Long, ClassLoader>();
    public SomeAbstractBase put(SomeAbstractBase so) {
        ClassLoader old = cache.getCacheService().getContextClassLoader();
        try {
            cache.getCacheService().setContextClassLoader(so.getClass().getClassLoader());
            classLoaders.put(so.getId(), so.getClass().getClassLoader());
            return (SomeAbstractBase) cache.put(so.getId(), so);
        } finally {
            cache.getCacheService().setContextClassLoader(old);
   public SomeAbstractBase get(Long id) {
        ClassLoader old = cache.getCacheService().getContextClassLoader();
        try {
            cache.getCacheService().setContextClassLoader(classLoaderMap.get(id));
            return (SomeAbstractBase) cache.get(id);
        } finally {
            cache.getCacheService().setContextClassLoader(old);
   }

Answer 1

Jarell wrote:
Hi Andy,
andypiper wrote:
Setting the CCL of the CacheService is a one-shot deal, it cannot actually be changed once set (you have to shutdown the service and restart to do something different).Completely forgot about this as you mentioned in another thread.
You can also set the bundle CL as the CCL for invocations, but this may not always be necessary.How do I do this? I want it to be flexible enough to accomodate any future implementation that will be deployed in the osgi environment.Implement BeanClassLoaderAware, then when you make the call do something like:
ClassLoader saveCcl = Thread.currentThread().getContextClassLoader();
try {
Thread.currentThread().setContextClassLoader(beanClassLoader);
// do call here
} finally {
Thread.currentThread().setContextClassLoader(saveCcl);
Note that if you are invoking OSGi services then Spring-DM will do this for you if you set the appropriate attribute on the reference definition.
We use hessian in our product which has much the same requirements as you and we actually found that it was difficult to avoid doing DynamicImport-Package: * in the bundle doing the serialization.