Logical, server-managed entities must implement this interface.
Allows for notifications that a plugin has been either created or destroyed.
Interface to listen for plugin manager events.
The admin console plugin.
A default Module implementation that basically avoids subclasses having to implement the whole Module interface.
Configuration to use when creating caches.
Task that will return the bind interface and ports being used by the admin console of the node where the task will be executed.
Task that will be run in each cluster node to learn if the specified plugin is installed or not.
A helper class to read cache configuration data for a plugin and register the defined caches with the cache factory.
A simple registry of cache configuration data for plugins.
ClassLoader for plugins.
Represents the data model used to represent development mode within the Jive Openfire plugin framework.
Servlet is used for retrieval of plugin icons.
Loads and manages plugins.
The plugin servlet acts as a proxy for web requests (in the admin console) to plugins.
An enumberation for plugin license agreement types.
The microkernel core of the server is a simple, flexible, nested container framework defined in this package.
The container model consists of three primary participants:
The nesting nature of containers allows a tree-like server
architecture with a root 'bootstrap container' with core modules, and
child containers with their own modules. Child containers by default
inherit and extend the bootstrap container's classpath and services
while being protected from implementation details of any modules,
containers, or services in layers above them. In some cases, child
containers may have restricted views or access to upper levels of the
tree (e.g. a user plug-in container that allows users to add arbitrary
Copyright © 2003-2008 Jive Software.