Uses of Class
org.codehaus.plexus.summit.AbstractSummitComponent

Packages that use AbstractSummitComponent

org.codehaus.plexus.summit.display
org.codehaus.plexus.summit.exception
org.codehaus.plexus.summit.pipeline
org.codehaus.plexus.summit.pipeline.valve
org.codehaus.plexus.summit.pull
org.codehaus.plexus.summit.pull.tools
org.codehaus.plexus.summit.renderer
org.codehaus.plexus.summit.resolver
org.codehaus.plexus.summit.rundata

Uses of AbstractSummitComponent in org.codehaus.plexus.summit.display

Subclasses of AbstractSummitComponent in org.codehaus.plexus.summit.display

class

AbstractDisplay

class

ClassicBufferedDisplay A ClassicDisplay takes a Resolution computed by the ClassicResolver and displays the resolution according to the Turbine 2.x model where we have something like the following: +------------------------------------------------+ | DefaultLayout.vm | | +--------------------------------------------+ | | | TopNavigation.vm | | | +--------------------------------------------+ | | | | +--------------------------------------------+ | | | | | | | | | | | $screenViewContent | | | | | | | | | | | +--------------------------------------------+ | | | | +--------------------------------------------+ | | | TopNavigation.vm | | | +--------------------------------------------+ | +------------------------------------------------+ This example uses Velocity templates as an example but this Display strategy could just as easily be applied to a set of JSPs.

Uses of AbstractSummitComponent in org.codehaus.plexus.summit.exception

Subclasses of AbstractSummitComponent in org.codehaus.plexus.summit.exception

class

DefaultExceptionHandler

Uses of AbstractSummitComponent in org.codehaus.plexus.summit.pipeline

Subclasses of AbstractSummitComponent in org.codehaus.plexus.summit.pipeline

class	AbstractPipeline Flexible implementation of a Pipeline.
class	SummitPipeline Flexible implementation of a Pipeline.

Uses of AbstractSummitComponent in org.codehaus.plexus.summit.pipeline.valve

Subclasses of AbstractSummitComponent in org.codehaus.plexus.summit.pipeline.valve

class	AbstractValve Valve that can be used as the basis of Valve implementations.
class	ActionValve
class	CreateViewContextValve
class	DetermineTargetValve
class	DisplayValve
class	ResolverValve

Uses of AbstractSummitComponent in org.codehaus.plexus.summit.pull

Subclasses of AbstractSummitComponent in org.codehaus.plexus.summit.pull

class	PullToolReleaseValve PullToolValve uses the PullService to populate the ViewContext.
class	PullToolValve PullToolValve uses the PullService to populate the ViewContext.

Uses of AbstractSummitComponent in org.codehaus.plexus.summit.pull.tools

Subclasses of AbstractSummitComponent in org.codehaus.plexus.summit.pull.tools

class

TemplateRenderer This class is a hack that allows you to render templates via the old Turbine 3 style.

Uses of AbstractSummitComponent in org.codehaus.plexus.summit.renderer

Subclasses of AbstractSummitComponent in org.codehaus.plexus.summit.renderer

class	AbstractRenderer Base class from which all Renderers are derived.
class	VelocityRenderer A Renderer that can process Velocity templates.

Uses of AbstractSummitComponent in org.codehaus.plexus.summit.resolver

Subclasses of AbstractSummitComponent in org.codehaus.plexus.summit.resolver

class	AbstractResolver The base class from which all Resolvers are derived.
class	ClassicResolver This resolving strategy emulates the Turbine 2.x process of matching a target up with: A layout module A layout view A screen module The navigation views are stated explicitly in the layout view according to the resolving process in Turbine 2.x so this resolver doesn't have to do any work in this respect.
class	SimpleResolver

Uses of AbstractSummitComponent in org.codehaus.plexus.summit.rundata

Subclasses of AbstractSummitComponent in org.codehaus.plexus.summit.rundata

class	AbstractRunData The base class from which all RunData implementations are derived.
class	DefaultRunData