Eclipse Community Forums: EclipseLink

Help

Home

Home » Eclipse Projects » EclipseLink » @OneToMany SortedSet

Show: Today's Messages :: Show Polls :: Message Navigator

@OneToMany SortedSet [message #741657]

Wed, 19 October 2011 19:15

Marc

Messages: 12
Registered: September 2011

Junior Member

In order to guarantee preserving the order after any add/remove operation, I'm trying to use a TreeSet attribute under a jpa project as follows :

@OneToMany(mappedBy="b")
private TreeSet<A> manyA;

'A' does implement the Comparable<A> interface.

The problem is that i'm getting the following compile time error :
Target entity for "manyA" is not defined.

If i replace TreeSet by Set the error disappears, i tried the SortedSet interface but still having the same error.

I'm using eclipselink 2.3.0, and Eclipse EE IDE Indigo.

Is there any way to make eclipseLink accept SortedSet mapped attributes?

Report message to a moderator

Re: @OneToMany SortedSet [message #748405 is a reply to message #741657]

Mon, 24 October 2011 17:23

James Sutherland

Messages: 1939
Registered: July 2009
Location: Ottawa, Canada

Senior Member

Is this a compile error, or just a warning from Eclipse's JPA support?

If you just ignore the warning, does it work?

You can give the targetEntity in the annotation and probably make the warning go away.

JPA only allows Collection, List and Set for collection types, but EclipseLink will support any implementation is you use EAGER. For LAZY support, one of the three interfaces is currently required. You could use Set, and assign a TreeSet to it, however EclipseLink would use its LAZY Set, IndirectSet when restoring from the database.

So try,
@OneToMany(targetEntity=A.class, fetch=EAGER, mappedBy="b")

James : Wiki : Book : Blog : Twitter

Report message to a moderator