Uses of Package
org.jivesoftware.openfire.container
Packages that use org.jivesoftware.openfire.container
Package
Description
Database connection code.
Ad-Hoc Commands implementation (XEP-0050).
The microkernel core of the server is a simple, flexible, nested
container framework defined in this package.
Service discovery implementation (XEP-0030).
Implementation of Entity Capabilities (XEP-0115).
Implementation of SOCKS5 Bytestreams (XEP-0065).
IQ class implementations.
Implementation of Multi-User Chat (XEP-0045).
Implementation of Multi-User Chat (XEP-0045).
Implementation of Personal Eventing via Pubsub (XEP-0163).
Implementation of Publish-Subscribe (XEP-0060).
Provides classes for managing the roster.
Classes that provide the "check for update" service or the "get available plugins" service.
-
Classes in org.jivesoftware.openfire.container used by org.jivesoftware.database
-
Classes in org.jivesoftware.openfire.container used by org.jivesoftware.openfireClassDescriptionA default Module implementation that basically avoids subclasses having to implement the whole Module interface.Logical, server-managed entities must implement this interface.Manages plugins.
-
Classes in org.jivesoftware.openfire.container used by org.jivesoftware.openfire.archiveClassDescriptionA default Module implementation that basically avoids subclasses having to implement the whole Module interface.Logical, server-managed entities must implement this interface.
-
Classes in org.jivesoftware.openfire.container used by org.jivesoftware.openfire.audit.spiClassDescriptionA default Module implementation that basically avoids subclasses having to implement the whole Module interface.Logical, server-managed entities must implement this interface.
-
Classes in org.jivesoftware.openfire.container used by org.jivesoftware.openfire.cluster
-
Classes in org.jivesoftware.openfire.container used by org.jivesoftware.openfire.commandsClassDescriptionA default Module implementation that basically avoids subclasses having to implement the whole Module interface.Logical, server-managed entities must implement this interface.
-
Classes in org.jivesoftware.openfire.container used by org.jivesoftware.openfire.componentClassDescriptionA default Module implementation that basically avoids subclasses having to implement the whole Module interface.Logical, server-managed entities must implement this interface.
-
Classes in org.jivesoftware.openfire.container used by org.jivesoftware.openfire.containerClassDescriptionConfiguration 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.Logical, server-managed entities must implement this interface.Plugin interface.A simple registry of cache configuration data for plugins.ClassLoader for plugins.Allows for notifications that a plugin has been either created or destroyed.Manages plugins.Interface to listen for plugin manager events.A bean-like representation of the metadata of a plugin.
-
Classes in org.jivesoftware.openfire.container used by org.jivesoftware.openfire.discoClassDescriptionA default Module implementation that basically avoids subclasses having to implement the whole Module interface.Logical, server-managed entities must implement this interface.
-
Classes in org.jivesoftware.openfire.container used by org.jivesoftware.openfire.entitycapsClassDescriptionA default Module implementation that basically avoids subclasses having to implement the whole Module interface.Logical, server-managed entities must implement this interface.
-
Classes in org.jivesoftware.openfire.container used by org.jivesoftware.openfire.filetransferClassDescriptionA default Module implementation that basically avoids subclasses having to implement the whole Module interface.Logical, server-managed entities must implement this interface.
-
Classes in org.jivesoftware.openfire.container used by org.jivesoftware.openfire.filetransfer.proxyClassDescriptionA default Module implementation that basically avoids subclasses having to implement the whole Module interface.Logical, server-managed entities must implement this interface.
-
Classes in org.jivesoftware.openfire.container used by org.jivesoftware.openfire.handlerClassDescriptionA default Module implementation that basically avoids subclasses having to implement the whole Module interface.Logical, server-managed entities must implement this interface.
-
Classes in org.jivesoftware.openfire.container used by org.jivesoftware.openfire.keystoreClassDescriptionA default Module implementation that basically avoids subclasses having to implement the whole Module interface.Logical, server-managed entities must implement this interface.
-
Classes in org.jivesoftware.openfire.container used by org.jivesoftware.openfire.mediaproxyClassDescriptionA default Module implementation that basically avoids subclasses having to implement the whole Module interface.Logical, server-managed entities must implement this interface.
-
Classes in org.jivesoftware.openfire.container used by org.jivesoftware.openfire.mucClassDescriptionA default Module implementation that basically avoids subclasses having to implement the whole Module interface.Logical, server-managed entities must implement this interface.
-
Classes in org.jivesoftware.openfire.container used by org.jivesoftware.openfire.muc.spiClassDescriptionA default Module implementation that basically avoids subclasses having to implement the whole Module interface.Logical, server-managed entities must implement this interface.
-
Classes in org.jivesoftware.openfire.container used by org.jivesoftware.openfire.netClassDescriptionA default Module implementation that basically avoids subclasses having to implement the whole Module interface.Logical, server-managed entities must implement this interface.
-
Classes in org.jivesoftware.openfire.container used by org.jivesoftware.openfire.pepClassDescriptionA default Module implementation that basically avoids subclasses having to implement the whole Module interface.Logical, server-managed entities must implement this interface.
-
Classes in org.jivesoftware.openfire.container used by org.jivesoftware.openfire.pubsubClassDescriptionA default Module implementation that basically avoids subclasses having to implement the whole Module interface.Logical, server-managed entities must implement this interface.
-
Classes in org.jivesoftware.openfire.container used by org.jivesoftware.openfire.rosterClassDescriptionA default Module implementation that basically avoids subclasses having to implement the whole Module interface.Logical, server-managed entities must implement this interface.
-
Classes in org.jivesoftware.openfire.container used by org.jivesoftware.openfire.sessionClassDescriptionA default Module implementation that basically avoids subclasses having to implement the whole Module interface.Logical, server-managed entities must implement this interface.
-
Classes in org.jivesoftware.openfire.container used by org.jivesoftware.openfire.spiClassDescriptionA default Module implementation that basically avoids subclasses having to implement the whole Module interface.Logical, server-managed entities must implement this interface.
-
Classes in org.jivesoftware.openfire.container used by org.jivesoftware.openfire.transportClassDescriptionA default Module implementation that basically avoids subclasses having to implement the whole Module interface.Logical, server-managed entities must implement this interface.
-
Classes in org.jivesoftware.openfire.container used by org.jivesoftware.openfire.updateClassDescriptionA default Module implementation that basically avoids subclasses having to implement the whole Module interface.Logical, server-managed entities must implement this interface.A bean-like representation of the metadata of a plugin.
-
Classes in org.jivesoftware.openfire.container used by org.jivesoftware.openfire.vcardClassDescriptionA default Module implementation that basically avoids subclasses having to implement the whole Module interface.Logical, server-managed entities must implement this interface.