Community
Participate
Working Groups
Happens only in field access case. After LoadPolicy loads OneToOne weaved value holder the corresponding attribute still not initialized. Weaving takes care of synchronizing it with the weaved vh - but only if the attribute accessed directly or through getter/setter. Reflectively accessed attribute is still not initialized.
Created attachment 176283 [details] suggested patch The patch extends approach taken by property access case to field access: WeavedObjectBasicIndirectionPolicy is set as an indirection policy in case of weaving of ObjectReferenceMapping for indirection. The only difference with property access case is that instead of the original setter method (i.e. setAddress) the weaved method is used (i.e. _persistence_set_address). To test the patch added attrAndVHContainSameObjectAfterGetRealAttributeValue for both fieldaccess and property access versions of SimpleSerializeFetchGroupTests.
The patch checked into both trunk and 2.1.1
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink