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

[scott.stark@jboss.org]

That still sounds potentially too coarse. I would look at the cache as message oriented tree where a usage context has to bind a serialization manager to obtain a typed view of the cache data. When there are puts/gets to the cache, it needs to be done through the context "connection" to the cache messaging layer that has the correct serialization manager.

I view a deployment wanting their own cache as wanting their own typed view, and namespace, but they may want to automagically integrate into the deployment env transport that binds distributed cache contexts together. Not overriding the transport/clustered configuration gets into being able to take a deployment and have it inherrit aspects of its environment.


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

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