Re: [hibernate-dev] [OGM] When is AssociationKey serialized?
2014/2/3 Sanne Grinovero <sanne(a)hibernate.org>
On 3 February 2014 13:33, Emmanuel Bernard
<emmanuel(a)hibernate.org> wrote:
> Hum, with the fact that this object now points to metadata, I wonder if
> we should force EhCache, Map and Infinispan to have their own version of
> EntityKey / RowKey and AssociationKey (or an appropriate externalizer).
Ok to consider it, but let's keep an eye on performance requirements:
allocating twice the objects which are strictly necessary is probably
not going to help.
But using a backend-specific externalizer would avoid that, right? This
appears as the preferred option to me so far.
Maybe if these where interfaces, each GridDialect could make his own
type ?
Maybe, but these types are instantiated by the core engine, so we'd have to
enhance GridDialect with (factory) methods for creating instances.
Sanne
>
> Emmanuel
>
> On Mon 2014-02-03 11:56, Gunnar Morling wrote:
>> Hi,
>>
>> I'm wondering why org.hibernate.ogm.grid.AssociationKey implements
>> Serializable. When is it actually serialized?
>>
>> I'm suspecting the answer is "never", as the type of the
"metadata"
member
>> is not serializable, so I'd expect a NotSerializableException to be
raised.
>>
>> If so, does anything speak against making AssociationKey not implement
>> Serializable?
>>
>> Thanks,
>>
>> --Gunnar
>> _______________________________________________
>> hibernate-dev mailing list
>> hibernate-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/hibernate-dev
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev