| |
|
| |
You can help automate library management by creating events for drafts, documents, folders, or the library. To customize the handling of these events, you must create and deploy a custom event handler. This topic describes the basic concepts of event handlers. |
| |
|
| |
This topic shows you the event types that are compatible with each event source. |
| |
|
| |
After the event handler is triggered, you can access the data by calling the events API. An event object is passed in when onEvent method is called. |
| |
|
| |
Administrators can disable event handling for the entire server. |
| |
|
| |
Use the OSGi console to install the event handler after it has been developed and enabled. |
| |
|
| |
After declaring subscriptions for event handler, use events API to register the event handler in the bundle activator. For more information about the bundle activator, refer to OSGi documentation. |
| |
|
| |
After implementing EventActionHandler, define the subscriptions to manage when the event handler is triggered. Adding Java annotations is an easy way to accomplish this task. |
| |
|
| |
The event handler is a common OSGi bundle. Refer to OSGi documentation to learn more about creating a bundle. This topic focuses on the additional work needed to create an event handler once the OSGi bundle has been created. |