Community
Participate
Working Groups
In bug 315242 we fixed an issue with fetch groups and weaving by ignoring variables called _persistence_fetchGroup in our metadata processing code. This fix needs to be revisited. Some suggestions to solve the problem: 1. Add an EclipseLink specific annotation to get EclipseLink to ignore the field 2. Add a property that affects whether weaved fetch groups are serializable and default it to false
Revisit for 2.2.0
Deferred to future as part of 2.2.0 bug scrub.
If you use static weaving and metadata complete any weaved fields (fetch groups, lazy 1-1, etc.) will be auto mapped. I am extending the existing fix to ignore all EclipseLink weaved fields, as the original fix was only ignoring fetch groups. But the issue is bigger than this, if any other framework is also weaving in fields and using @Transient to have them ignored by JPA (such as we do for JAXB adding @XmlTransient), then we will auto map these fields. Perhaps we should not auto map any @Transient fields, or have an option that allows this to be set. Workarounds include dynamic weaving, method access, marking the fields as Java transient, using our xml flag to ignore default mappings.
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink
