[jboss-cvs] JBossAS SVN: r93195 - projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Thu Sep 3 21:08:21 EDT 2009
Author: irooskov at redhat.com
Date: 2009-09-03 21:08:21 -0400 (Thu, 03 Sep 2009)
New Revision: 93195
Modified:
projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US/Microcontainer.xml
Log:
updated with tech review info
Modified: projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US/Microcontainer.xml
===================================================================
--- projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US/Microcontainer.xml 2009-09-03 23:40:05 UTC (rev 93194)
+++ projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US/Microcontainer.xml 2009-09-04 01:08:21 UTC (rev 93195)
@@ -4,9 +4,21 @@
<chapter><title>Microcontainer</title>
<indexterm><primary>MC</primary><see>JBoss Microcontainer</see></indexterm>
-<para>JBoss Enterprise Application Platform 5.0 uses the Microcontainer to integrate enterprise services together with a Servlet/JSP container, EJB container, deployers and management utilities in order to provide a standard Java EE environment. If you need additional services then you can simply deploy these on top of Java EE to provide the functionality you need. Likewise any services that you do not need can be removed by changing the configuration. You can even use the Microcontainer to do this in other environments such as Tomcat and GlassFish by plugging in different classloading models during the service deployment phase.</para>
-<para>Since JBoss Microcontainer is very lightweight and deals with POJOs, it can also be used to deploy services into a Java ME runtime environment. This opens up new possibilities for mobile applications that can now take advantage of enterprise services without requiring a full JEE application server. </para>
-<para>As with other lightweight containers, JBoss Microcontainer uses dependency injection to wire individual POJOs together to create services. Configuration is performed using either annotations or XML depending on where the information is best located. Unit testing is made extremely simple thanks to a helper class that extends JUnit to setup the test environment, allowing you to access POJOs and services from your test methods using just a few lines of code.
+<para>JBoss Enterprise Application Platform 5.0 uses the Microcontainer to integrate enterprise services
+ together with a Servlet/JSP container, EJB container, deployers and management utilities in order to
+ provide a standard Java EE environment. If you need additional services then you can simply deploy
+ these on top of Java EE to provide the functionality you need. Likewise any services that you do not
+ need can be removed by changing the configuration. You can even use the Microcontainer to do this in
+ other environments such as Tomcat and GlassFish by plugging in different classloading models during
+ the service deployment phase.
+ Since JBoss Microcontainer is very lightweight and deals with POJOs, it can also be used to deploy
+ services into a Java ME runtime environment. This opens up new possibilities for mobile applications
+ that can now take advantage of enterprise services without requiring a full JEE application server.
+ As with other lightweight containers, JBoss Microcontainer uses dependency injection to wire
+ individual POJOs together to create services. Configuration is performed using either annotations or
+ XML depending on where the information is best located. Unit testing is made extremely simple thanks
+ to a helper class that extends JUnit to setup the test environment, allowing you to access POJOs and
+services from your test methods using just a few lines of code.
</para>
<section><title>An overview of the Microcontainer modules</title>
@@ -32,11 +44,11 @@
<literal>classloader</literal> new peer classloader model, prepared to handle OSGi bundle model.
</para>
</listitem>
- <listitem>
+ <!-- <listitem>
<para>
The <literal>container</literal> module contains: reflection, the integration point for manipulating class information at runtime (for example, overriding annotations or obtaining an aop instance advisor), joinpoint (the joinpoint model including the join point factory), classadaptor (the integration and configuration spi) and metadata (the base metadata types and repository).
</para>
- </listitem>
+ </listitem> -->
<listitem>
<para>
<literal>dependency</literal> management is handled by the controller. The controller is the core component for keeping track of contexts to make sure the configuration and lifecycle are done in the correct order including dependencies and classloading considerations.
@@ -44,42 +56,52 @@
</listitem>
<listitem>
<para>
- <literal>deployers</literal> load components from various models, POJOs, JMX, spring, Java EE, etc. into the Microcontainer runtime.
+ <literal>deployers</literal> load components from various models (for example, POJOs, JMX, spring, Java EE) into the Microcontainer runtime.
</para>
</listitem>
<listitem>
<para>
- <literal>kernel</literal> kernel defines the core kernel spi including, boostrap, configuration, POJO deployments, dependency, events, bean metadata, and bean registry.
+ <literal>kernel</literal> defines the core kernel spi including, boostrap, configuration, POJO deployments, dependency, events, bean metadata, and bean registry.
</para>
</listitem>
<listitem>
<para>
- The <literal>managed</literal> module defines the base objects defining the management view of a component.
+ The <literal>managed</literal> and <literal>metatype</literal> modules define the base objects defining the management view of a component.
</para>
</listitem>
<listitem>
<para>
- The <literal>metatype</literal> module defines the base types found in the management view of a component.
+ <literal>guice-int</literal> contains the integration classes for Guice.
</para>
</listitem>
<listitem>
<para>
- <literal>guice-int</literal> contains the integration classes for guice.
+ <literal>osgi-int</literal> contains the integration classes that adapt the OSGi model onto the Microcontainer.
</para>
</listitem>
+ <!-- <listitem>
+ <para><literal>reliance-identity</literal> defines identity as a MC POJO service</para>
+ </listitem> -->
<listitem>
- <para>
- <literal>osgi-int</literal> contains the integration classes that adapt the OSGi model onto the Microcontainer.
- </para>
+ <para><literal>reliance-rules</literal> defines your dependencies with Drools</para>
</listitem>
+ <!-- <listitem>
+ <para><literal>reliance-jbpm</literal> defines your dependencies with jBPM</para>
+ </listitem> -->
<listitem>
- <para><literal>reliance-identity</literal> defines identity as a MC POJO service</para>
+ <para>
+ <literal>reflect</literal> is the integration point for manipulating class information at runtime.
+ </para>
</listitem>
<listitem>
- <para><literal>reliance-rules</literal> defines your dependencies with Drools</para>
+ <para>
+ <literal>mdr</literal> is the generic metadata repository. It handles scoped metadata lookups.
+ </para>
</listitem>
<listitem>
- <para><literal>reliance-jbpm</literal> defines your dependencies with jBPM</para>
+ <para>
+ <literal>vfs</literal> represents Virtual File System. It's an abstraction layer to identify known file system issues in a single module.
+ </para>
</listitem>
<listitem>
<para>
@@ -91,23 +113,25 @@
</section>
<section><title>Configuration</title>
- <para>To configure the Microcontainer bootstrap you can use the <filename>JBOSS_HOME/server/<server_configuration>/conf/bootstrap.xml</filename> and <filename>JBOSS_HOME/server/<server_configuration>/conf/bootstrap/*.xml</filename> files where <emphasis><server_configuration></emphasis> represents the name of the server profile, for example, <emphasis>all</emphasis>, <emphasis>default</emphasis> or <emphasis>minimal</emphasis>. The <filename>bootstrap.xml</filename> simply references Microcontainer deployment descriptors that should be loaded in the indicated order. The current <emphasis>default</emphasis> profile <filename>bootstrap.xml</filename> references are:
+ <para>To configure the Microcontainer bootstrap you can use the <filename>JBOSS_HOME/server/<server_configuration>/conf/bootstrap.xml</filename> and <filename>JBOSS_HOME/server/<server_configuration>/conf/bootstrap/*.xml</filename> files where <emphasis><server_configuration></emphasis> represents the name of the server profile, for example, <emphasis>all</emphasis>, <emphasis>default</emphasis>, <emphasis>standard</emphasis>, <emphasis>web</emphasis> or <emphasis>minimal</emphasis>. The <filename>bootstrap.xml</filename> simply references Microcontainer deployment descriptors that should be loaded in the indicated order. The current <emphasis>default</emphasis> profile <filename>bootstrap.xml</filename> references are:
</para>
<itemizedlist>
+ <listitem><para><filename>logging.xml</filename> - logging manager and bridge config </para></listitem>
<listitem><para><filename>vfs.xml</filename> - JBoss VFS caching beans</para></listitem>
<listitem><para><filename>classloader.xml</filename> - the root class loading beans for the peer class loading model</para></listitem>
<listitem><para><filename>aop.xml</filename> - JBoss AOP integration and AspectManager beans</para></listitem>
<listitem><para><filename>jmx.xml</filename> - JBoss JMX kernel initialization</para></listitem>
<listitem><para><filename>deployers.xml</filename> - Core deployers for -<filename>jboss-beans.xml</filename> and -service.xml</para></listitem>
- <listitem><para><filename>bindings.xml</filename> - Rewrite of the ServiceBindingManager as a POJO bean</para></listitem>
- <listitem><para><filename>profile-repository.xml</filename> - full featured repository based profile service referenced by <filename>bootstrap.xml</filename></para></listitem>
+ <listitem><para><filename>profile.xml</filename> - full featured repository based profile service referenced by <filename>bootstrap.xml</filename></para></listitem>
+ <!--<listitem><para><filename>bindings.xml</filename> - Rewrite of the ServiceBindingManager as a POJO bean</para></listitem>
+ <listitem><para><filename>profile-repository.xml</filename> - full featured repository based profile service referenced by <filename>bootstrap.xml</filename></para></listitem>-->
</itemizedlist>
<para>The main beans are:
<itemizedlist>
<listitem>
- <para><emphasis>ProfileService</emphasis> : This bean loads the deployments associated with the named server profile, <emphasis>default</emphasis>, <emphasis>all</emphasis> or the name that is passed to the server using the <code>-c</code> option. It's an extension of always looking to the filesystem <filename>server/name/conf/jboss-service.xml</filename> and <filename>server/name/deploy</filename> to load deployments.
+ <para><emphasis>ProfileService</emphasis> : This bean loads the deployments associated with the named server profile, <emphasis>default</emphasis>, <emphasis>all</emphasis> or the name that is passed to the server using the <code>-c</code> option. It's an extension of always looking to the filesystem <filename>server/name/conf/jboss-service.xml</filename>, <filename>server/name/deployers</filename> and <filename>server/name/deploy</filename> to load deployments.
</para>
</listitem>
<listitem>
@@ -115,7 +139,7 @@
</para>
</listitem>
<listitem>
- <para><emphasis>MainDeployer</emphasis> : An update of the JMX based MainDeployer from earlier versions to a one based on the Microcontainer, <classname>JBoss5VirtualFileSystem</classname>, and Virtual Deployment Framework(VDF). Deployer aspects are registered with the MainDeployer as an ordered list via inject of the deployers property.
+ <para><emphasis>MainDeployer</emphasis> : An update of the JMX based MainDeployer from earlier versions to one based on the Microcontainer, Virtual File System, and Virtual Deployment Framework(VDF). Deployer aspects are registered with the MainDeployer as an ordered list via inject of the deployers property.
</para>
</listitem>
<listitem>
@@ -127,15 +151,15 @@
</para>
</listitem>
<listitem>
- <para><emphasis>FileStructure</emphasis> : this bean is a structural deployment aspect which recognizes well know deployment file types specified by suffix.
+ <para><emphasis>FileStructure</emphasis> : this bean is a structural deployment aspect which recognizes well know deployment file types specified by FileManager and suffix.
</para>
</listitem>
<listitem>
- <para><emphasis>AspectDeployer</emphasis> : handles aop descriptor deployments.
+ <para><emphasis>AspectDeployer</emphasis> : handles AOP descriptor deployments.
</para>
</listitem>
<listitem>
- <para><emphasis>BeanDeployer</emphasis> : this bean translates <filename>deployer-beans.xml</filename> into <classname>KernelDeployment</classname> for the descriptor beans.
+ <para><emphasis>BeanDeployer</emphasis> : this bean translates <filename>*-jboss-beans.xml</filename> into <classname>KernelDeployment</classname> for the descriptor beans.
</para>
</listitem>
<listitem>
@@ -147,7 +171,7 @@
</para>
</listitem>
<listitem>
- <para><emphasis>SARDeployer</emphasis> : this bean is a port of the legacy JMX <classname>SARDeployer</classname> to the VDF. It handles the legacy <filename>jboss-service.xml</filename> style of mbean deployment descriptors and maps this into a <classname>ServiceDeployment</classname> POJO.
+ <para><emphasis>SARDeployer</emphasis> : this bean is a port of the legacy JMX <classname>SARDeployer</classname> to the VDF. It handles the legacy <filename>*-service.xml</filename> style of mbean deployment descriptors and maps this into a <classname>ServiceDeployment</classname> POJO.
</para>
</listitem>
<listitem>
@@ -162,14 +186,14 @@
<para><emphasis>JMXKernel</emphasis> : Manages the instantiation of a JMX kernel and <classname>MBeanServer</classname> in the jboss domain. It is used by the <classname>SARDeployer</classname>. It will be used by other management deployment aspects in the future to expose kernel beans via JMX.
</para>
</listitem>
- <listitem>
+ <!-- <listitem>
<para><emphasis>VFSDeployerScanner</emphasis> : A scanner bean that loads the deployers directory contents into the basic profile service.
</para>
</listitem>
<listitem>
<para><emphasis>VFSDeploymentScanner</emphasis> : A scanner bean that loads the deploy directory contents into the basic profile service.
</para>
- </listitem>
+ </listitem> -->
<listitem>
<para><emphasis>HDScanner</emphasis> : A bean that queries the profile service for changes in deploy directory contents and redeploys updated content, undeploys removed content, and add new deployment content to the profile service.
</para>
@@ -183,7 +207,7 @@
<section><title>References</title>
-<para>More information on the JBoss Microcontainer project can be obtained from <ulink url="http://labs.jboss.com/jbossmc/"/>. </para>
+ <para>More information on the JBoss Microcontainer project can be obtained from <ulink url="http://www.jboss.org/jbossmc/"/>. </para>
</section>
</chapter>
More information about the jboss-cvs-commits
mailing list