Package com.arsdigita.cms.lifecycle

Provides a set of classes to manage and apply lifecycles to content items.

See:
          Description

Interface Summary
LifecycleListener This class registers the action to perform with a lifecycle/phase begins or ends.
 

Class Summary
Duration Utility methods for lifecycle durations.
Initializer Initializes the scheduler thread to fire all the events for the lifecycles or phases that have just began or ended.
Lifecycle This class represents a Publication Lifecycle for a Content Item.
LifecycleDefinition Definition for a publication lifecycle.
LifecycleDefinitionCollection This class contains a collection fo Lifecycle Definition
LifecycleEvent This event class stores the information necessary for the firing of events in the LifecycleListener class.
LifecycleService This class provides method in associating ACSObject to Lifecycle and methods to access the association.
NotifyLifecycleListener LifecycleListener implementation which sends out a notification that the item is about to expire.
Phase This class represents a phase in Publication Lifecycle for a Content Item.
PhaseCollection This class contains a collection for Phases
PhaseDefinition Definition for a phase in a publication life lifecycle.
PhaseDefinitionCollection This class contains a collection fo Phase Definitions
PublishLifecycleListener This class makes an item live while it is in a lifecycle.
Scheduler Scheduler thread to fire all the events for the lifecycles or phases that have just began or ended.
 

Exception Summary
PublishingException Lifecycle exception
 

Package com.arsdigita.cms.lifecycle Description

Provides a set of classes to manage and apply lifecycles to content items.

The lifecycle engine is used to control the post-production processing of a content item. It is flexible enough to handle automatic scheduling of multiple deployment stages.

CMS uses the concept of lifecycles and phases to model the deployment of content items. A Lifecycle is a period of time in which a content item is deployed. Each lifecycle is associated with a start time and, optionally, a stop time. Phases are relevant time periods within a particular lifeycle. Like a lifecycle, each phase is associated with a start time and, optionally, an end time. The start time of the earliest phase within a lifecycle is the start time of that life cycle; the end time of the latest phase within a lifecycle is the end time of that lifecycle. The phases in a lifecycle need not be contiguous and can overlap with other phases.

Templates are used to generalize a class of lifecycles and phases. The relation between lifecycle templates and phase templates is analogous to that of lifecycles and phases. Phase templates differ only slightly from the actual phases. Instead of having a start and end time, phase templates are associated with a delay and duration. The delay is the length of time of from the start of the lifecycle up to the time that the phase becomes active. The duration is the length of time that the phase remains active.



Copyright (c) 2004 Red Hat, Inc. Corporation. All Rights Reserved. Generated at July 19 2004:2352 UTC