Community
Participate
Working Groups
Build Identifier: build=20101206_v100_20111212_1418 I find that sometimes I see a null element in a transaction, after having inserted a element into a parent onetomany relationship. Think it's the bug listed in https://bugs.eclipse.org/bugs/show_bug.cgi?id=247041. Isn't this solved ? Reproducible: Sometimes Steps to Reproduce: 1.insert a element in a parent entity 2. in a new transaction the parens elementlist contains a null element Parent has this attributes: @OneToMany(mappedBy = "hopl", cascade={CascadeType.REMOVE}) @OrderBy("startdato") @XmlTransient public Collection<SkolefagPaHoldPlacering> getVeuSkolefagPaHoldPlacCollection() { return this.veuSkolefagPaHoldPlacCollection; }
Does this fail on our 2.3.1 release? (I'm having trouble reading the build identifier) If so, please provide, at least, some pseudo code that deomonstrates the problem.
Setting target and priority. See the following page for the meanings of these fields: http://wiki.eclipse.org/EclipseLink/Development/Bugs/Guidelines Community: Please vote for this bug if it is important to you. Votes are one of the main criteria we use to determine which bugs to fix next.
@OrderBy on a Collection using a @OneToMany mapping works in the nightly tests. If this is still an issue, please update with the information requested by Tom - the version being used and the code to reproduce the issue.
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink