----- Original Message -----
Sent: Thursday, June 04, 2009 4:56
PM
Subject: Re: [eclipselink-dev] Bug
249037: JPA 2.0 persisting list item index.The second core patch checked into
trunk.
Andrei, I have some questions for you about that unfinished JPA
support. I'm looking at the orm_2_0.xsd in trunk and wondering if the
order-column contiguous and base attributes are new and haven't made it into
the jpa spec yet? The version of the spec I have is from
3/13/09.
Also, I see mention of an annotation called OrderColumnValidation
on the EclipseLink wiki. Is this something that is going to be pushed to
the JPA 2.0 spec, or will it be purely an EclipseLink feature? Are there
other EclipseLink specific features related to the order column that I have
not seen?
thanks,
Karen
On 6/2/2009 5:55
PM, Andrei Ilitchev wrote:
What's added in the patch:
1. Functionality to find and fix "holes"
in order in the db;
2. Functionality to query by order index;
3.
Support for list order field in secondary table (SALARY table
for
Employee class).
What is not done yet, but soon will be
done.
1. No JPA support (neither feature nor tests)
What likely
won't be done any time soon.
1. No duplicate support - except
DirectCollectionMapping.
Code review by James is pending.
Please send the feedback.
Thanks,
Andrei
_______________________________________________
eclipselink-dev mailing list
eclipselink-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-dev
_______________________________________________
eclipselink-dev
mailing
list
eclipselink-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-dev
