Interface Command
-
- All Known Implementing Classes:
AbstractGetLocaleCommand,AbstractSetLocaleCommand,ChainBase,CopyCommand,DispatchCommand,DispatchLookupCommand,LookupCommand,PathInfoMapper,PortletGetLocaleCommand,PortletSetLocaleCommand,RemoveCommand,RequestParameterMapper,ServletGetLocaleCommand,ServletPathMapper,ServletSetLocaleCommand
public interface CommandA
Commandencapsulates a unit of processing work to be performed, whose purpose is to examine and/or modify the state of a transaction that is represented by aContext. IndividualCommands can be assembled into aChain, which allows them to either complete the required processing or delegate further processing to the nextCommandin theChain.Commandimplementations should be designed in a thread-safe manner, suitable for inclusion in multipleChains that might be processed by different threads simultaneously. In general, this implies thatCommandclasses should not maintain state information in instance variables. Instead, state information should be maintained via suitable modifications to the attributes of theContextthat is passed to theexecute()command.Commandimplementations typically retrieve and store state information in theContextinstance that is passed as a parameter to theexecute()method, using particular keys into theMapthat can be acquired viaContext.getAttributes(). To improve interoperability ofCommandimplementations, a useful design pattern is to expose the key values used as JavaBeans properties of theCommandimplementation class itself. For example, aCommandthat requires an input and an output key might implement the following properties:private String inputKey = "input"; public String getInputKey() { return (this.inputKey); } public void setInputKey(String inputKey) { this.inputKey = inputKey; } private String outputKey = "output"; public String getOutputKey() { return (this.outputKey); } public void setOutputKey(String outputKey) { this.outputKey = outputKey; }And the operation of accessing the "input" information in the context would be executed by calling:
String input = (String) context.get(getInputKey());
instead of hard coding the attribute name. The use of the "Key" suffix on such property names is a useful convention to identify properties being used in this fashion, as opposed to JavaBeans properties that simply configure the internal operation of this
Command.- Version:
- $Revision: 480477 $ $Date: 2006-11-29 08:34:52 +0000 (Wed, 29 Nov 2006) $
- Author:
- Craig R. McClanahan
-
-
Field Summary
Fields Modifier and Type Field Description static booleanCONTINUE_PROCESSINGstatic booleanPROCESSING_COMPLETECommands should returnPROCESSING_COMPLETEif the processing of the givenContexthas been completed.
-
Method Summary
All Methods Instance Methods Abstract Methods Modifier and Type Method Description booleanexecute(Context context)Execute a unit of processing work to be performed.
-
-
-
Field Detail
-
CONTINUE_PROCESSING
static final boolean CONTINUE_PROCESSING
Commands should return
CONTINUE_PROCESSINGif the processing of the givenContextshould be delegated to a subsequentCommandin an enclosingChain.- Since:
- Chain 1.1
- See Also:
- Constant Field Values
-
PROCESSING_COMPLETE
static final boolean PROCESSING_COMPLETE
Commands should return
PROCESSING_COMPLETEif the processing of the givenContexthas been completed.- Since:
- Chain 1.1
- See Also:
- Constant Field Values
-
-
Method Detail
-
execute
boolean execute(Context context) throws java.lang.Exception
Execute a unit of processing work to be performed. This
Commandmay either complete the required processing and returntrue, or delegate remaining processing to the nextCommandin aChaincontaining thisCommandby returningfalse- Parameters:
context- TheContextto be processed by thisCommand- Returns:
trueif the processing of thisContexthas been completed, orfalseif the processing of thisContextshould be delegated to a subsequentCommandin an enclosingChain- Throws:
java.lang.Exception- general purpose exception return to indicate abnormal terminationjava.lang.IllegalArgumentException- ifcontextisnull
-
-