Community
Participate
Working Groups
EclipseLink supports basicIndirection which requires objects use a ValueHolderInterface attribute type which needs to be supported in orm.xml.
The eclipselink-orm.xml must allow developers the ability to select our various indirection policies. When using annotations EclispeLink will default based on the type used in the class when a relationship is specified as LAZY. This does mean that we should support the direct usage of ValueHolderInterface in a domain model with annotations but its usage should be quite rare and definitely a lower priority. As for the XML we should have support for defining the indirection policy in all relationship mappings. <indirection-policy>Basic</indirection-policy> This will allow a enum set of values as well as an option for a user to provide a fully qualified class name where the class implements IndirectionPolicy.
For models where ValueHolderInterface is used we should address processing to ensure it works with the weaver. @ManyToOne(fetch=FetchType.LAZY, targetEntity=Employee.class) private ValueHolderInterface manager; We will defer support for proxy-indirection from the 1.0 release
These JPA enhancements were accidentally assigned to 1.1.1.
Moving to 2.1 where our goal is to have the eclipselink-orm.xsd fully support all native features currently available in the deployment XML XSD
Updating priority due to revised bug categorization process. See the following page for details: http://wiki.eclipse.org/EclipseLink/Development/Bugs/Guidelines#Priority_and_Target_Milestone If you feel the updated priority is incorrect, please send an email to eclipselink-users@eclipse.org.
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink
