public interface ServerPluginServiceMBean
ServerPluginService service.
This essentially is the server that starts and stops the master plugin container
that manages all server-side plugins.| Modifier and Type | Field and Description |
|---|---|
static ObjectName |
OBJECT_NAME |
static String |
OBJECT_NAME_STR |
| Modifier and Type | Method and Description |
|---|---|
MasterServerPluginContainer |
getMasterPluginContainer()
Returns the master server plugin container that will be responsible for managing all plugins of all types and their classloaders.
|
File |
getServerPluginsDirectory()
Returns the directory where the server plugins are found.
|
boolean |
isMasterPluginContainerStarted()
Returns
true if the master plugin container has be started. |
boolean |
isStarted()
Returns
true if this service has been started. |
void |
restartMasterPluginContainer()
Convienence method that first does a
stopMasterPluginContainer() and then a startMasterPluginContainer(). |
void |
start()
Starts the service but will not start the
master plugin container. |
void |
startMasterPluginContainer()
Starts the
master plugin container which will load in all plugins, start them and then
schedule all jobs for all plugins. |
void |
startMasterPluginContainerWithoutSchedulingJobs()
Similar to
startMasterPluginContainer(), but this will not tell the master plugin container
to schedule any jobs yet. |
void |
stop()
Shuts down this service along with the
master plugin container. |
void |
stopMasterPluginContainer()
Stops the
master plugin container which will shuts down all plugins. |
static final String OBJECT_NAME_STR
static final ObjectName OBJECT_NAME
void start()
master plugin container. After the server
fully initializes, it should only then start the master server-side plugin container.void stop()
master plugin container.void startMasterPluginContainer()
master plugin container which will load in all plugins, start them and then
schedule all jobs for all plugins. You cannot start the plugin container unless this service has
been started. If the master plugin container is already started,
this does nothing and returns. You must ensure the job scheduler is started prior to calling this method.void stopMasterPluginContainer()
master plugin container which will shuts down all plugins. If the master
plugin container is already shutdown, this does nothing and returns.void restartMasterPluginContainer()
stopMasterPluginContainer() and then a startMasterPluginContainer().void startMasterPluginContainerWithoutSchedulingJobs()
startMasterPluginContainer(), but this will not tell the master plugin container
to schedule any jobs yet. Usually this is only
called when the server itself is starting up and it wants to start the master PC but it has not yet
started the scheduler. In this case, after this method is called, the caller must ensure the scheduler is
started and then tell the master PC to schedule all its plugin jobs.startMasterPluginContainer()MasterServerPluginContainer getMasterPluginContainer()
null if not startedboolean isStarted()
true if this service has been started. This does not necessarily mean the
master plugin container has be started - see isMasterPluginContainerStarted() for that.true if this service has been startedboolean isMasterPluginContainerStarted()
true if the master plugin container has be started.
Note that this is not an indication if this service has started - see isStarted() for that.
But, if the master plugin container has been started, then by definition this service has also been started.true if the master plugin container has been startedFile getServerPluginsDirectory()
Copyright © 2008-2014 Red Hat, Inc.. All Rights Reserved.