SVN Commit: Bug#272215, 251181, 242035 - Cache coordination, do not send
changes for objects configured for no synchronization, JPA config, invalidation
API
https://bugs.eclipse.org/bugs/show_bug.cgi?id=272215
https://bugs.eclipse.org/bugs/show_bug.cgi?id=251181
Also, Bug#251181, Bug#212270
Changes:
- Test fixed to ensure change set not sent when descriptor configured to
not send changes.
- Added test for sending invalidation using API for RCM
- Updated some tests.
- Added cache coordination configuration to persistence unit properties.
- Fixed field and timestamp locking to merge coordination changes.
- Pass class-loader for exception resource lookups.
- Made some optimizations, changes to MergeManager, WriteLockManager
- Removed prepare for synchronization step in coordination (just pass
descriptor when creating change set)
- Added API to IdentityMapAccessor to send invalidation across cluster,
fixed some comments.
- Updated ChangeSets to use List/Map and generics.
- Added descriptor to ObjectChangeSet (need for aggregates, and avoids
lookups).
- Change UnitOfWorkChangeSet to key changes by class instead of class
name (as transient anyway).
- Avoid broadcasting changes if configured to not send changes.
- Invalidated instead of refresh, out of version objects with cache
coordination.
- Added some generics to UnitOfWorkImpl
- Removed removal of unchanged changeset during merge (and clone for
changes sets list).
- Cleaned up some RCM comments, methods (Removed TopLink refs), changed
defaults (channel, etc.) to be named EclipseLink not TopLink.
- Updated test script to run clustered concurrency tests in WLS.
- Added tests for clustered concurrency testing in a server.
- Added support to EntityManagerSetupImpl for cache coordination
settings.
- Avoid throwing an error in MetadataProcessor if there are two orm.xml
files, switch to logging warning as this can occur in some configs (same file,
two locations).
Code Review: Gord (pending)