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

[bstansberry@jboss.com]

"scott.stark at jboss.org" wrote : At some level, but it does not have to be the core. Having the namespace be typed and potentially scoped I'm sure complicates interaction of what might be shared/common aspects. If the cache is used in pure in memory mode, there should be no need to serialize the data. If you through in a cache loader, then you have another serialization path. It certainly needs the correct class loader, but its separate from the current jgroups message issue. Is there a common serialization abstraction for these two cases?
  | 

Currently no.  There is some recent discussion around unifying this somewhat (see http://jira.jboss.com/jira/browse/JBCACHE-879.)

I'm not aware of any serialization problems related to classloaders, presumably because cacheloader operations are typically performed by application threads where the TCCL has visibility to the required classes. That could certainly break down though in a more exotic use case.

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

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