| Summary: | NullPointerException in JoinedAttributeManager class with cursor | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | jean marie turc <jmturc> |
| Component: | Eclipselink | Assignee: | Project Inbox <eclipselink.orm-inbox> |
| Status: | CLOSED DUPLICATE | QA Contact: | |
| Severity: | major | ||
| Priority: | P2 | CC: | christopher.delahunt, david.minsky, tom.ware |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
jean marie turc
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. I've observed the same issue when reproducing the following bug: Bug 361860 - Using ScrollableCursor with 1:M joining produces incorrect results I can confirm that when testing the patch attached to this bug, the NPE is no longer observed. The underlying cause is the same - the cursor row is being nulled out when still needed when joining is being used. *** This bug has been marked as a duplicate of bug 361860 *** The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink |