Package org.infinispan.commands

package org.infinispan.commands
Commands that operate on the cache, either locally or remotely. This package contains the entire command object model including interfaces and abstract classes. Your starting point is probably ReplicableCommand, which represents a command that can be used in RPC calls.

A sub-interface, VisitableCommand, represents commands that can be visited using the visitor pattern. Most commands that relate to public

invalid reference
API methods tend to be VisitableCommands, and hence the importance of this interface.

The Visitor interface is capable of visiting VisitableCommands, and a useful abstract implementation of Visitor is

invalid reference
, which allows you to create interceptors that intercept command invocations adding aspects of behavior to a given invocation.
Manik Surtani
  • Class
    Base class for those commands that can carry flags.
    Base class for commands that carry topology id.
    An abstract implementation of a Visitor that delegates all visit calls to a default handler which can be overridden.
    Represents an unique identified for non-transaction write commands.
    A factory to build commands, initializing and injecting dependencies accordingly.
    Commands of this type manipulate data in the cache.
    Flags modify behavior of command such as whether or not to invoke certain commands remotely, check cache store etc.
    Commands correspond to specific areas of functionality in the cluster, and can be replicated using the GlobalInboundInvocationHandler.
    Deprecated, for removal: This API element is subject to removal in a future version.
    since 11.0, please implement
    invalid reference
    This is a marker interface to indicate that such commands will never be replicated and hence will not return any valid command IDs.
    A command that contains metadata information.
    Specifically used to create un-initialized ReplicableCommands from a byte stream.
    The core of the command-based cache framework.
    Interface to be implemented when the command can define a single segment for its operation.
    Some of the commands sent over the wire can only be honored by the receiver if the topology of the cluster at delivery time is still 'compatible' with the topology in place at send time (eg.
    A type of command that can accept Visitors, such as DDAsyncInterceptor.