On 10/10/11 9:33 AM, Galder Zamarreño wrote:
Interesting article Jason.
This might be handy for Infinispan because in the discussions we had
in Lisbon, we're talking about being able to have the module
identifier included in the payload for AS envs. Your solution would
make our lifes easier.
Couple of questions:
- Is ModularClassResolver a class of JBoss Marshalling or AS?
It's in JBoss Marshalling.
- What happens if you use ModularClassResolver in a non-AS
environment? Could it delegate to a backup class resolver? I think
this could be useful.
It currently requires that both communication peers use JBoss Modules,
not necessarily both be AS7. For EJB3 we were going to write a variant
that filtered the module information and loaded classes on the classpath
to support embedded client usage in a non-modularized client. Not sure
if that was done yet or not, its not much work though.
On Sep 27, 2011, at 11:03 PM, Jason T. Greene wrote:
> Hi Everyone,
> I wrote up an article today that talks about the issues (and
> solutions) of serializing in a modular (or any multi-classloader)
> If you are developing any kind of component that sends data on AS7,
> then please give this a read.
> As an example of the application of this information, ejb3 remote
> communication is being developed to follow solution 3.
> -- Jason T. Greene JBoss AS Lead / EAP Platform Architect JBoss, a
> division of Red Hat
> _______________________________________________ jboss-as7-dev
> mailing list jboss-as7-dev(a)lists.jboss.org
-- Galder Zamarreño Sr. Software Engineer Infinispan, JBoss Cache
Jason T. Greene
JBoss AS Lead / EAP Platform Architect
JBoss, a division of Red Hat