| Summary: | Lazy fetched ManyToOne field of an embedded object of a newly persisted entity will be set to null on commit | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Igor Mukhin <iimuhin> | ||||
| Component: | Eclipselink | Assignee: | Nobody - feel free to take it <nobody> | ||||
| Status: | CLOSED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P2 | CC: | iimuhin, tom.ware | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Igor Mukhin
Created attachment 175094 [details]
JUnit Test that fails
This is a small Maven project than demonstrates the bug.
It contains of
- two @entity classes and one @embeddable,
- persistence.xml,
- pom.xml (does static weaving after compiling)
- JUnit test that fails
To run:
- unpack the zip
- run "mvn test"
- Test will fail on second Assert.assertNotNull
Important point: weaving required to reproduce pom.xml references EclipseLink 2.2.0-M1, but the same is with 2.1.0 Setting target and priority. See the following page for details of the meanings of these fields: http://wiki.eclipse.org/EclipseLink/Development/Bugs/Guidelines It looks like it was fixed in 2.3.0 Closing because of above comment. The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink |