Download Livelink WCM Server Programming Guide for the WCM Java API

Transcript
Chapter 4 Event processing
4.2 Preparation events
The
PrepareEvent
Interface
Preparation events for website-related and system-related actions are represented
by the PrepareEvent interface. They are fired before the underlying action is
executed. This provides the possibility to review the impending status change and,
if necessary, prevent it (by a VetoException). Each preparation event contains a
reference to the related WCM object as an argument.
Note: Preparation events for website-related and system-related actions are
only available on the master Content server.
The following events belong to this category:
•
PREPARE_ASSIGN_WORKFLOW
•
PREPARE_CHECKIN_OBJECT
•
PREPARE_CHECKOUT_OBJECT
•
PREPARE_CREATE_OBJECT
•
PREPARE_DELETE_OBJECT
•
PREPARE_DESTROY_OBJECT
•
PREPARE_FORWARD_WORKFLOW
•
PREPARE_OBJECT_CHANGE_METADATA
•
PREPARE_REJECT_OBJECT_TO_EDIT
•
PREPARE_RELEASE_OBJECT
•
PREPARE_REMOVE_WORKFLOW
•
PREPARE_SUBMIT_OBJECT_TO_QA
•
PREPARE_UNDO_CHECKOUT_OBJECT
For detailed information on the individual events and the associated arguments,
refer to the Javadoc. For an example of a server agent that throws a VetoException,
refer to “Vetoing metadata changes” on page 135.
The
DeploymentPrep
areEvent
Interface
Preparation events for deployment-related actions are represented by the
DeploymentPrepareEvent interface. Before a persistently stored page is created or
changed, the corresponding deployment system informs registered event listeners
by means of the preparation event PREPARE_FILE_CHANGED. This provides the
possibility to review the impending change and, if necessary, prevent it (by a
VetoException).
Notes:
•
56
A veto against page generation usually results in inconsistencies, i.e. the
page does not reflect the current state of the WCM object any longer. For
this reason, you should not use this veto possibility.
Livelink WCM Server
WM090700-PJA-EN-1