Community
Participate
Working Groups
Currently the TopLink invalidation API does not support transparent propagation of a cache invalidation request to other TopLink instances participating in a clustered deployment configuration. Currently the work around is make use of the RemoteCommandManager and one or more custom RemoteCommands to explicitly propagate the invalidation request to other clustered TopLink instances. Please consider enhancing the cache invalidation API to automatically propagate the invalidation request. RemoteCommands could make use of the same arguments that the cache invalidation API does: Expression; VectorOfPrimaryKeys + Target Class; Vector of Objects (expensive). Would also be nice to be able to pass a Vector of PrimaryKeys and Target Class.
Added boolean option to the invalidation APIs to broadcast to the cluster. Only did the primary key related APIs, not the Expression.
Mass update to change fixed in target.
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink