philippe van dyck wrote:
this is not a problem but FYI when entities are JSon-ized, the identity
is repeated at the very begining and during the properties
enumeration... maybe the last one could be skipped ?
example :
{"/identity":"22b1471b9.L/","type":"com.netzep.chilliz.domain.model.assembly.voucher.LotEntity","version":"288298b7-1d04-454f-b321-b11bdc6264f5-3","modified":1251738267099,"/properties/":{"size":2,"/identity":"22b1471b9.L/","activated":true},"associations":{"zone":"LeBarAGilles.Z"},"manyassociations":{"vouchers":["6d947e258.V","7344928d6.V"]}}
Right, the question is basically whether to make Identity.identity() a
computed property or not. On the one hand it would "save" some space,
and on the other it would make indexing more troublesome, as it would
have to special-case identity, as it would no longer be part of the
regular set of persistent properties. I would vote for keeping it as it
is for this reason.
/Rickard
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
