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

[scott.stark@jboss.org]

We need to separate services from runtime aspects tied to what are in general type scoped contexts. If an aspect needs to deal with typed data associated with a potentially scoped deployment, that aspect has to be presented the class loader to use. It also needs to have a life-cycle associated with the deployment as it needs to be recycled if the type system needs to be updated.

In the past we hid these type issues by encapsulating the data in MarshalledObject/MarshalledValue instances so that the common service layers did not in fact see the type.


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

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