| Summary: | Cache CoordinationType issue of the subclass | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Daniel Lo <daniel.lo> |
| Component: | Eclipselink | Assignee: | David Minsky <david.minsky> |
| Status: | CLOSED WORKSFORME | QA Contact: | Project Inbox <eclipselink.orm-inbox> |
| Severity: | normal | ||
| Priority: | P2 | CC: | david.minsky, tom.ware |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Daniel Lo
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 |