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

[scott.stark@jboss.org]

Ok, then the disconnect is why control of serialization requires a region based configuration. The first problem would seem to be that even the typed rpc functionality of jgroups should have a serialization api that allows shared use of a channel with marshalling/unmarshalling of types based on application endpoints with different type systems. Serialization is an aspect of the user, not an inherent function of the jbc or jgroups. The default configuration of the serialization aspect needs to be triggered by an application level aspect, which could pick up the app thread context class loader. 

It seems we are picking up a naive standalone component behavior where serialization is an inherent function of the messaging layer. That is not the case for any service that needs to integrate into jbossas, esb, etc. 

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

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