User: starksm
Date: 01/04/02 14:33:24
Modified: src/docs basicconfiguration.xml howtombeans.xml
Log:
It is the ServiceControl MBean that manages service depdencies, not the
ConfigurationSerivce MBean.
Revision Changes Path
1.7 +8 -9 manual/src/docs/basicconfiguration.xml
Index: basicconfiguration.xml
===================================================================
RCS file: /cvsroot/jboss/manual/src/docs/basicconfiguration.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- basicconfiguration.xml 2001/04/02 03:25:40 1.6
+++ basicconfiguration.xml 2001/04/02 21:33:24 1.7
@@ -138,7 +138,7 @@
<para> Configuration file jboss.conf typically
contains only those core service MBeans that are
necessary to achieve the initial "bootstrap" of JBoss . These services
include the classpath extension inclusion mechanism shown in
- <xref linkend = "jboss.conf-excerpt"/> , logging ,configuration service,
etc.</para>
+ <xref linkend = "jboss.conf-excerpt"/> , logging ,configuration service,
service control, etc.</para>
<figure id = "jboss.conf-excerpt">
<title>Excerpt from jboss.conf</title>
@@ -215,19 +215,18 @@
</para>
- <para>The jboss.jcml file is loaded by the
org.jboss.configuration.ConfigurationService MBean. This service acts much like the
standard JMX MLet class in that it loads and configures MBeans, but it also manages
dependencies between MBeans as long as the MBean interface conforms to a certain
pattern described by the org.jboss.util.ServiceMBean interface. This interface allows
for the ordered initialization, starting, stopping and destorying of MBeans. The
ordering is based on the order in which MBeans are specified in the jboss.jcml file.
See <xref linkend = "howto.mbeans"/> for the details of creating an MBean with
depedencies on other MBeans.</para>
- </listitem>
-
- <listitem>
- <para id =
"jboss.dependencies-file">jboss.dependencies</para>
+ <para>The jboss.jcml file is loaded by the
org.jboss.configuration.ConfigurationService MBean. This service acts much like the
standard JMX MLet class in that it loads and configures MBeans. The dependencies
between MBeans are managed by the org.jboss.util.ServiceControl MBean. The
ServiceControl MBean listens for REGISTRATION_NOTIFICATION and
UNREGISTRATION_NOTIFICATION JMX events to determine which MBeans are available. The
order of rgistration determines the order of initialization and startup. The
ServiceControl expects that MBeans which require depdendency management to conform to
the org.jboss.util.Service interface. This interface allows for the ordered
initialization, starting, stopping and destorying of MBeans. The ordering is based on
the order in which MBeans are specified in the jboss.jcml file. See <xref linkend =
"howto.mbeans"/> for the details of creating an MBean with depedencies on other
MBeans.</para>
+ </listitem>
+ <listitem>
+ <para id =
"jboss.dependencies-file">jboss.dependencies</para>
<para> For the reason of simplicity and ease of
configuration JBoss's DependancyManager
- was deprecated in 2.1 release, so this file is no longer used.</para>
+ was deprecated in 2.1 release, so this file is no longer used.</para>
<para> Now all MBeans listed in jboss.jcml have
"vertical" dependency on each other.
For example, JNDI provider is required for DataSource wrappers since
DataSource wrapper has to store reference to itself in JNDI, thus JNDI
provider
- MBean has to be listed before DataSource wrapper. See <xref linkend =
"howto.mbeans"/> for the details of the depedency mechanism.</para>
-
+ MBean has to be listed before DataSource wrapper. See <xref linkend =
"howto.mbeans"/> for the details of the depedency mechanism.</para>
+
</listitem>
1.2 +30 -5 manual/src/docs/howtombeans.xml
Index: howtombeans.xml
===================================================================
RCS file: /cvsroot/jboss/manual/src/docs/howtombeans.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- howtombeans.xml 2001/04/02 03:25:40 1.1
+++ howtombeans.xml 2001/04/02 21:33:24 1.2
@@ -1,17 +1,42 @@
<?xml version = "1.0" encoding = "UTF-8"?>
-<section id="howto.mbeans">
+<section id = "howto.mbeans">
<title>How to Integrate Custom MBeans</title>
<para>
<author>
<firstname>Scott</firstname>
<surname>Stark</surname>
</author>
- <email>[EMAIL PROTECTED]</email>
+ <email>[EMAIL PROTECTED]</email>
</para>
<section>
<title>Introduction</title>
- <para>If you want to add services to the JBoss server, the best way to
do that is to write your own JMX MBeans. Then they can be configured in jboss.jcml
like the core JBoss MBeans. The best way for your EJBs to access your new services is
to make them accessible via JNDI.</para>
- <para>More to come...
- </para>
+ <para>The best way to add services to the JBoss server is to write
your own JMX MBeans. An MBean is a Java object which implement resources and their
instrumentation interfaces as defined in the Java Management Extensions(JMX)
specification. Once written they are added to JBoss using the jboss.jcml which is used
to configure the core JBoss MBeans. The best way for your EJBs to access your new
services is to make them accessible via JNDI.</para>
+ <para>There are two classes of MBeans; those that are independent of
JBoss services and those that are dependent on JBoss services. MBeans that are
independent of JBoss services are the trival case and can be written per the JMX
specification and added to a JBoss server by adding their MLET tag to the jboss.conf
file. Writing an MBean that relieas on a JBoss service like naming requires one to
follow the JBoss service pattern.</para>
+ <section>
+ <title>The ConfigurationService MBean</title>
+ <para>JBoss manages dependencies between its MBeans via a
custom MBean that loads an xml variation of the standard MLet configuration file. This
custom MBean is implemented in the org.jboss.configuration.ConfigurationService class.
The ConfigurationService MBean is loaded when JBoss starts up by the JMX MLet due to
its entry in the jboss.conf file. The jboss.jcml configuration is then loaded by
invoking loadConfiguration() on the ConfigurationService MBean. The loadConfiguratoin
method performs the following steps:</para>
+ <procedure>
+ <step>
+ <para>Parse the jboss.jcml file and
instantiate all MBeans</para>
+ </step>
+ <step>
+ <substeps>
+ <step>
+ <para>Parse the optional
jboss-auth.jcml file and instantiate any MBeans that were not created by the parser of
the jboss.jcml file.</para>
+ </step>
+ <step>
+ <para>Apply the MBean
attribute settings from the jboss-auto.jcml file.</para>
+ </step>
+ </substeps>
+ </step>
+ <step>
+ <para>Apply the attribute settings from the
jboss.jcml file.</para>
+ </step>
+ </procedure>
+ </section>
+ </section>
+ <section>
+ <title>Writing JBoss MBean Services</title>
+ <para/>
</section>
</section>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
