See: Description
| Interface | Description |
|---|---|
| CommandsFactory |
A factory to build commands, initializing and injecting dependencies accordingly.
|
| DataCommand |
Commands of this type manipulate data in the cache.
|
| FlagAffectedCommand |
Commands affected by Flags should carry them over to the remote nodes.
|
| LocalCommand |
This is a marker interface to indicate that such commands will never be replicated and hence will not return any
valid command IDs.
|
| ReplicableCommand |
The core of the command-based cache framework.
|
| VisitableCommand |
A type of command that can accept
Visitors, such as CommandInterceptors. |
| Visitor |
| Class | Description |
|---|---|
| AbstractFlagAffectedCommand |
Base class for those commands that can carry flags.
|
| AbstractVisitor |
An abstract implementation of a Visitor that delegates all visit calls to a default handler which can be overridden.
|
| CommandsFactoryImpl | |
| RemoteCommandsFactory |
Specifically used to create un-initialized
ReplicableCommands from a byte stream. |
| RemoveCacheCommand |
Command to stop a cache and remove all its contents from both
memory and any backing store.
|
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 Cache 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 CommandInterceptor, which allows you to create
interceptors that intercept command invocations adding aspects of behavior to a given invocation.Copyright © 2012 JBoss by Red Hat. All Rights Reserved.