Table of Contents
Advertisement
Service architecture (JMX)
Services are the atomic unit of a JRun server, and all feature components must contain a
service view—whether that view is a wrapper, a helper class, a factory, or the functional
class itself—in order to be plugged into JRun. All JRun components, even the bootstrap
components that manage the JMX spine, are services.
Each service, regardless of its vertical functional purpose, participates in the following
lifecycle stages:
init
start
stop
resident in memory and capable of quickly being restarted.
destroy
memory.
When the JRun server starts, services that are externalized as XML entries in jrun.xml are
automatically created, initialized, and started, and their attributes are automatically
configured. The services are automatically stopped and destroyed when the JRun server
shuts down. You can invoke the
running server in order to restart a service. The following list contains more detail on the
service lifecycle:
1 All services are created and their attributes set in the order in which their entries
appear in jrun.xml.
2 All services have their
services appear in jrun.xml.
3 All services have their
services appear in jrun.xml. Each service whose
bound to JNDI.
4 On receipt of a shutdown event, all services have their
reverse order in which they appear in jrun.xml, and JNDI-enabled services are
removed from JNDI.
5 All services have their
appear in jrun.xml.
80
Chapter 8 JRun Services
Lets you establish values for nonmanaged instance variables.
Binds the service to JNDI and prepares it for use.
Removes the service from JNDI and it becomes unusable, although still
Disposes of the service's resources, the service itself is removed from
methods invoked, based on the order in which the
init
start
destroy
and
methods any number of times on a
start
stop
methods invoked, based on the order in which the
bindToJNDI
methods invoked in reverse order in which they
attribute is set to true is
methods invoked in
stop
Advertisement
Table of Contents
