| Summary: | Three PessimisticLocking tests of jpa jpql model failed with assertion on GlassFish V3 only | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Yiping Zhao <yiping.zhao> | ||||
| Component: | Eclipselink | Assignee: | Nobody - feel free to take it <nobody> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | christopher.delahunt, tom.ware | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Yiping Zhao
Tests are failing in 2.0.3 due to a test case issue - they will only pass on an extended persistence context. The tests in 2.1 and 2.2 have been corrected in revision 7250, but this was not applied to 2.0.x. Simply, test was checking version numbers from a detached entity and expecting that a later transaction would result in it changed. Outside the server, the extended persitence context meant the entity is still managed, and so the version does get correctly incremented on flushes. Simple test fix is to add employee = em.find(Employee.class, employee.getId()); before the assert so the test gets the correct value to use in the comparison. Created attachment 183801 [details]
test fix
test case fix for these 3 tests.
Fix checked into 2.0.3 in revision 8559 *** Bug 320117 has been marked as a duplicate of this bug. *** The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink |