| Summary: | Cache Coordination fails to keep OneToMany with order column updated when using CacheCoordinationType.SEND_NEW_OBJECTS_WITH_CHANGES | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Tom Ware <tom.ware> | ||||
| Component: | Eclipselink | Assignee: | Tom Ware <tom.ware> | ||||
| Status: | CLOSED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P2 | CC: | eclipselink.foundation-inbox | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Tom Ware
Created attachment 203707 [details]
proposed fix
Final change was to allow the orderedAddObjectList to be serialized. There is very little cost to this because other variables containing the same change sets are already serialized. Fix checked into trunk, 2.1, 2.2 and 2.3 to follow Review Chris Delahunt - pending Added test to RCM Distributed Model Tested with JPA and Core LRG Fix checked into 2.3.x, 2.2.x and 2.1.x The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink |