Home >> All >> org >> infohazard >> maverick >> [ flow Javadoc ]

• org.infohazard.maverick.flow: Javadoc index of package org.infohazard.maverick.flow.


Package Samples:

• org.infohazard.maverick.flow

Classes:

• CommandBase: Base class for implementing a Maverick Command . Implementors must define getView(java.lang.String) 55 . CommandBase obtains a View name by calling its Controller's go 55 method, and then invokes the View's go 55 method. The ModelLifetime interface is honored. After invoking View.go, if the model object is an instance of ModelLifetime, its discard 55 method is called.
• Shunt: The Shunt interface allows Maverick to automagically determine which of a set of views should be executed based on some arbitrary characteristic of the request. Views are associated with modes in the Maverick configuration, and the Shunt is responsible for identifying the proper mode based on the request. The canonical example of a Shunt is the LanguageShunt, which uses the Accept-Language header to choose among views with modes like "en", "fr", etc. More complicated Shunts might allow regexes or other sophisticated expressions in the mode string. Individual Shunt instances are associated with ...
• AbstractControllerFactory: Base class for controller factories. Creates (what appears to be) a singleton controller object appropriate for the type of controller specified in the XML, including single-use controllers. If no controller is specified, a special do-nothing controller is returned. If you want to use a custom controller factory, it is advisable to extend from this class and override either the interface method (createController) or override one or more of the template methods (getControllerClass, getControllerInstance and initializeController).
• Transform: The Transform interface allows some sort of arbitrary transformation on a set of input data. It is the relatively static object in the Maverick configuration object graph which represents a specific transform node in the config file. The actual work of performing a transformation step during actual request procesing is done by an instance of TransformationStep, which Maverick asks the Transform object to create.
• ControllerSingleton: ControllerSingleton serves two purposes: First, the presence of this interface on a Controller class indicates to the framework that the controller should be defined as a singleton rather than instantiating a fresh instance for every request. Second, it provides a method to initialize the singleton controller with the relevant XML data from the configuration file.
• Command: The Command is the highest entry point of workflow outside of the Dispatcher . For a base implementation, see CommandBase .
• TransformStep: The TransformStep defines a transformation step in a single request. It is used and then disposed of. It provides convenient facades for most of the usual output mechanisms that views and previous transforms might want. Unlike a Transform, a TransformStep is used in a single request and then thrown away.
• Controller: Controller is the interface that all command controllers must implement. A controller which implements this interface (and not ControllerSingleton) will have a new instance instantiated for every request.
• ShuntFactory: Pluggable modules which build Shunts must implement this interface and then be defined in the <modules> section of the Maverick config file. One factory is created to build all Shunts.
• MasterFactory: Factory for creating View and Transform objects. This calls out to specific instances of ViewFactory and TransformFactory to actually create the objects.
• MaverickContext: MaverickContext is the concrete class which implements all the other contexts. Having one object minimizes object creation and data copying.
• CommandFactory: Factory for creating Command objects based on some preloaded context (such as global views) and an XML command node. created January 28, 2002
• ThrowawayControllerAdapter: This adapter masquerades as a singleton controller but actually creates single-use instance controllers. created January 27, 2002
• LastStep: Simple transformation step which dumps to the real output. There are NO subsequent steps! This is the end of the line.
• ModelLifetime: If a model implements this interface, method(s) will be called so that the model object can manage internal resources.
• ViewRegistry: Factory for defining global view objects which can then be referenced for the creation of individual commands.
• CommandMultipleViews: Command implementation which allows one of several views to be determined by the controller result.
• NoSuitableModeException: Exception which indicates that a Shunt was unable to pick a mode based on current request state.
• ControllerContext: ControllerContext defines the methods and data available to a controller for a single request.
• TransformContext: TransformContext defines the methods and data available to a transform for a single request.
• Loader: Builds the tree of flow objects which process Maverick commands. created January 27, 2002
• ViewContext: ViewContext defines the methods and data available to a view for a single request.
• ViewWithTransforms: ViewWithTransforms is a decorator that sets transforms when rendering a view.
• ViewFactory: This interface allows user-defined view factories to be added to the system.
• ViewWithParams: ViewWithTransforms is a decorator that sets params when rendering a view.

Home | Contact Us | Privacy Policy | Terms of Service