M/R classes do have access to the cache so they can get a hold of the app's class
loader. But the tricky part is that the M/R tasks themselves need to be loaded from that
class loader first…
On 28 Jan 2013, at 14:01, Ales Justin <ales.justin(a)gmail.com> wrote:
> Ales - how could we bundle something like this as an AS module
and play nice with modular class loading there?
Well, I would say we're back to that discussion with AdvancedCache::withClassloader.
:-)
Same thing with M/R -- can it tap into app's CL?
Otherwise TCCL should do, in JEE env.
Or perhaps some init(Cache cache) on M/R classes, where it can get a hold of Cache,
which would then expose app' CL, via AC::withClassloader?
-Ales
> On 26 Jan 2013, at 21:55, Ales Justin <ales.justin(a)gmail.com> wrote:
>
>>> Would the thread context classloader be the right thing to use?
>>
>> It depends how Infinispan's M/R code handles setting of TCCL.
>> Specially in remote invocations.
>> But I would expect it to work.
>> Not the best, but good enough. :-)
>>
>>> Or, perhaps it can use ScriptEngine?
>>
>> What's ScriptEngine?
>>
>> -Ales
>>
>> _______________________________________________
>> infinispan-dev mailing list
>> infinispan-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/infinispan-dev
>
> --
> Manik Surtani
> manik(a)jboss.org
>
twitter.com/maniksurtani
>
> Platform Architect, JBoss Data Grid
>
http://red.ht/data-grid
>
>
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/infinispan-dev
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev