On Mar 17, 2011, at 3:22 PM, Manik Surtani wrote:
On 17 Mar 2011, at 14:16, David M. Lloyd wrote:
>>
>> Ah I see what you mean. Initially I thought you'd only need to
>> register the externaliser when you first encounter a new type (i.e.,
>> when a user defined type is first encountered with a put()), but this
>> may not be the case since on the remote node it may see the a new
>> magic number which may not be registered, and then you have a
>> problem.
>
> Marshalling will send Externalizers across the wire too, so the
> receiving side need not know about it in advance. The sending side can
> then do this kind of discovery safely. In addition, JBMAR already has
> the @org.jboss.marshalling.Externalize annotation which does just this.
>
> Unless you're talking about your own mechanism, anyway. Just thought
> I'd throw this bit out there.
Sweet. I think we can make this work then - even reusing JBM's annotations.
Hmmm, I wasn't aware of that either. I'll defo look into that for 5.0 -
https://issues.jboss.org/browse/ISPN-986
@Eduardo, this might solve your cache startup issue and the current need to define
Externalizers in advance.
--
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