On May 19, 2011, at 12:11 PM, Manik Surtani wrote: > Guys - what are we talking about? Specifying ClassLoaders is only meaningful > if storeAsBinary is set to true.
Ok, that was not clear to me throughout the discussion. > In general, any situation where you have code booted off different > ClassLoaders running in the same JVM and sharing the same cache (or cache > manager), you would *need* to set storeAsBinary to true to get around > deserialization issues on remote nodes. > > StoreAsBinary = false only really works for trivial cases where caches/cache > managers run in environments where only one cache loader is in effect. I.e., > *not* JBoss/Java EE/Hibernate/OSGi/etc. This is one of the reasons why we > considered setting storeAsBinary to true by default (and we see similar > techniques in competing data grids). This is clear now, thanks. > > Cheers > Manik > > > On 19 May 2011, at 10:55, Galder Zamarreño wrote: > >> would be different cache instances. The problem then is that if an RPC comes >> for "entities" cache and entity P1, which of the "entities" caches do I go >> for? You'd need to know which classloader P1 is living in the remote node >> and you'd have to now that at the Infinispan level to be able to store it in >> a non-binary format. > > -- > Manik Surtani > ma...@jboss.org > twitter.com/maniksurtani > > Lead, Infinispan > http://www.infinispan.org > > > > > _______________________________________________ > infinispan-dev mailing list > infinispan-dev@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/infinispan-dev -- Galder Zamarreño Sr. Software Engineer Infinispan, JBoss Cache _______________________________________________ infinispan-dev mailing list infinispan-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/infinispan-dev
