| Summary: | Null elements in onetomany relation entity | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Missing name Mising name <mejar.singh> |
| Component: | Eclipselink | Assignee: | Project Inbox <eclipselink.orm-inbox> |
| Status: | CLOSED WORKSFORME | QA Contact: | |
| Severity: | critical | ||
| Priority: | P2 | CC: | christopher.delahunt, tom.ware |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Missing name Mising name
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 |