|
||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |
public interface I_CmsModuleAction
Module action classes in OpenCms must implement this interface.
A module action class allows to perform special functions on certain
OpenCms lifecycle system events, like initialize(CmsObject, CmsConfigurationManager, CmsModule)
or
shutDown(CmsModule)
.
A_CmsModuleAction
Field Summary |
---|
Method Summary | |
---|---|
void |
initialize(CmsObject adminCms,
CmsConfigurationManager configurationManager,
CmsModule module)
Will be called by the OpenCms system during server startup. |
void |
moduleUninstall(CmsModule module)
Will be called if a module is uninstalled from an OpenCms system. |
void |
moduleUpdate(CmsModule module)
Will be called if the module this action instance belongs to is updated. |
void |
publishProject(CmsObject cms,
CmsPublishList publishList,
int publishTag,
I_CmsReport report)
Will be called during a the publish process after the resources have been published, but before the publish event is fired. |
void |
shutDown(CmsModule module)
Will be called by the OpenCms system during server shutdown. |
Methods inherited from interface org.opencms.main.I_CmsEventListener |
---|
cmsEvent |
Method Detail |
---|
void initialize(CmsObject adminCms, CmsConfigurationManager configurationManager, CmsModule module)
If a module requires special initialization code, this is a good place to to implement this functions.
Moreover, if the module requires special "one time" setup code, this should also be implemented here. For example if the module requires special DB tables to be created, you should implement a check if theses tables exist in this method, and if they don't exist create them as needed.
adminCms
- an initialized CmsObject with "Admin" permissionsconfigurationManager
- the initialized OpenCms configuration managermodule
- the module of this action instancevoid moduleUninstall(CmsModule module)
If you require special code to be executed if a module is uninstalled, implement it in this function.
Please note that there is no install()
method.
This is because the class loader will not have the module class
instance available after module installation/upload. If you
need to execute setup/install code, do this in the initialize(CmsObject, CmsConfigurationManager, CmsModule)
method during the next server startup.
This method is not called if the module this action instance belongs to
is "replaced". In this case moduleUpdate(CmsModule)
is called after the
new version of the module is installed.
module
- the module of this action instanceinitialize(CmsObject, CmsConfigurationManager, CmsModule)
void moduleUpdate(CmsModule module)
module
- the module of this action instance with the updated valuesvoid publishProject(CmsObject cms, CmsPublishList publishList, int publishTag, I_CmsReport report)
If you require special code to be executed after a resource is published, implement it in this function any analyze the publish list for "interesting" resources.
cms
- the user context the publish was executed withpublishList
- the list of published resourcespublishTag
- the publish tagreport
- the report to write messages tovoid shutDown(CmsModule module)
If a module requires special "clean up" functions, for example removing temporary files, this is a good place to implement this functions.
module
- the module of this action instance
|
||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |