[jboss-dev-forums] [Design of JBossCache] - Re: Default classloader for deserialization

[bstansberry@jboss.com]

Not in the AS if a scoped classloader is used, i.e.:

1) Cache is deployed from an ear/sar with a loader-repository configured
2) (I'm pretty sure) if cache is deployed from a webapp (e.g. a ServletContextListener does it at startup.)

If region-based marshalling isn't used, the classloader JBC uses to deserialize messages is the one that loaded JBC itself.  In the above cases, this classloader is a parent to the application's classloader, and thus can't see classes loaded by the parent classloader.

I mistakenly believed this would also cause problems with things deployed directly in /deploy (e.g. an ear without its own loader-repository) but experiments today show this is not the case.  I assume this means the default UCL for the deploy dir also loads the jars in /server/all/lib (where jboss-cache.jar and jgroups.jar are located.)

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3989719#3989719

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3989719