The issue came up with the TCK where we were trying to get JPOX to
recognize that an embedded PersistenceCapable in a join table can
have a unique identifying field. In the case of datastore identity,
this doesn't work because there is no primary key field in the
PersistenceCapable.
<proposed 18.14>
A portable mapping for arrays, collections, and maps will include a
primary key on the join table.
</proposed 18.14>
Why? I don't understand this at all. "Datastore identity" is
meaningless in this context, as embedded objects have no identity
according to the spec.
- Re: Issue 145: Mapping Map with embedded PersistenceCapab... Abe White
-