Checked into tunk.
Correction - set order to null after object removed from list
test to verify that order field is set to null after object removed
Also fixed handling of nulls
DirectCollectionMapping.valueFromRowInternalWithJoin: the fix I previously
in there (see bug 278126
caused creation of collections with a sole member
null - when an empty
collection was expected.
----- Original Message -----
Sent: Friday, June 19, 2009 12:30
Subject: [eclipselink-dev] Bug 249037:
JPA 2.0 persisting list item index
Checked into trunk:
JPA - added CorrectionType annotation and processing
to change the name of ORDER_COLUMN in inheriting class
using @AssociationOverride, but it didn't work: the
orderListField set in
the mapping in NBC remained the same as in
MappedSuperclass. For now using
the same order column name for both NBC and
Code review bu Guy is pending.