Community
Participate
Working Groups
The subclass' coordinationType is set to the default SEND_OBJECT_CHANGES instead of using the parent's coordinationType(SEND_NEW_OBJECTS_WITH_CHANGES for example), in another word, if an entity has a parent class, then its coordinationType is stucked to SEND_OBJECT_CHANGES, EclipseLink does not process the cache coordination by using its parent's coordinationType. For example, if the Specification super class has the following cache configuration: @Cache ( type=CacheType.FULL, expiry=-1, alwaysRefresh=false, disableHits=false, size=200, coordinationType=CacheCoordinationType.SEND_NEW_OBJECTS_WITH_CHANGES ) Then the subclass EquipmentSpecification cache coordination is always processed as SEND_OBJECT_CHANGES instead of SEND_NEW_OBJECTS_WITH_CHANGES.
Setting target and priority. See the following page for details of what this means: http://wiki.eclipse.org/EclipseLink/Development/Bugs/Guidelines
I looked into this issue, and could not reproduce this within EclipseLink trunk. It was observed that a subclass descriptor is initialized with the same CachePolicy cacheSynchronizationType as its parent descriptor, and new objects of the subclass type are sent with changes. In EclipseLink 2.2, The CachePolicy class was added, and is initialized for a child descriptor within ClassDescriptor initialize(AbstractSession session) Closing as closed, works for me; No additional fix code was added or changed in response to this bug.
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink
