if the deployment is up and running.
Although, I don't see how we need per application marshalling
configuration. The ModularClassResolver will work globally as deployment
module identity is globally unique.
--
Jason T. Greene
JBoss AS Lead / EAP Platform Architect
JBoss, a division of Red Hat
all OSGi requirements be handled by (1)? I would guess so, from what I
have read here, since the class loader is explicitly passed in when getting a
handle on a cache.
Definitely.
--
Jason T. Greene
JBoss, a division of Red Hat
___
infinispan-dev
it would have to
be tailored for each environment (OSGI and AS7 and so on).
So I think to ever justify it, it would take some very convincing
numbers that eager deserialization is indeed better.
--
Jason T. Greene
JBoss, a division of Red Hat
___
infinispan
CacheDelegateWithContext class to invoke those methods, but the public
API would remain the same.
You dont need to reuse the same impl. Just create a new delegate which
passes an extra invocation state parameter with ever call. The overhead
of that is tiny.
--
Jason T. Greene
JBoss, a division
@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev
___
infinispan-dev mailing list
infinispan-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev
--
Jason T. Greene
JBoss, a division of Red Hat
On 4/28/11 4:52 PM, Manik Surtani wrote:
On 27 Apr 2011, at 12:39, Jason T. Greene wrote:
Available here:
https://github.com/infinispan/infinispan/pull/278
The problem is basically that infinispan currently is using TCCL for all
class loading and resource loading. This has a lot
