Even if the Serializable/Externalizer rules do not allow this, I wonder whether if
anonymous classes that have externalizers associated to the would work...
Vladimir, I'm gonna this out and let you know if it works - good addition to testsuite
as well
On Mar 9, 2011, at 5:11 PM, Manik Surtani wrote:
Yeah that sucks. I suppose we just need to specify that anonymous
classes are not used. :/
On 9 Mar 2011, at 16:01, Vladimir Blagojevic wrote:
> Hey,
>
> I've sort of hit a snag with the current MapReduce design and
> serialization. Our MapReduceTask API allows users to specify Mapper,
> Reducer and Collator interfaces as anonymous classes [1]. However, we
> can not serialize instances of these classes as they are anonymous
> [2](see Note in section 1.10).
>
> Of course, users can specify static implementations of these interfaces
> and we can put a big warning notice about anonymous class
> implementations of Mapper, Reducer and Collator but our MapReduceTask
> fluent API itself nudges users to use anonymous classes :-(
>
> Not sure what to do! Ideas?
>
>
> [
1]http://community.jboss.org/wiki/InfinispanDistributedExecutionFramework...
>
>
[
2]http://download.oracle.com/javase/6/docs/platform/serialization/spec/se...
> _______________________________________________
> 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
Lead, Infinispan
http://www.infinispan.org
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev
--
Galder Zamarreño
Sr. Software Engineer
Infinispan, JBoss Cache