[jboss-cvs] JBossAS SVN: r82353 - projects/docs/community/5/Administration_And_Configuration_Guide/en-US.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Wed Dec 17 20:03:02 EST 2008
Author: scott.stark at jboss.org
Date: 2008-12-17 20:03:02 -0500 (Wed, 17 Dec 2008)
New Revision: 82353
Modified:
projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Architecture.xml
projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Microcontainer.xml
Log:
JBAS-6280, update bootstrap description
Modified: projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Architecture.xml
===================================================================
--- projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Architecture.xml 2008-12-18 00:59:03 UTC (rev 82352)
+++ projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Architecture.xml 2008-12-18 01:03:02 UTC (rev 82353)
@@ -151,4 +151,23 @@
</para>
+ <sect1 id="Architecture_Server_Bootstrap">
+ <title>The JBoss AS Bootstrap</title>
+ <indexterm><primary>JBossAS</primary><secondary>bootstrap</secondary></indexterm>
+ <para>The JBossAS 5 bootstrap is similar to the JBossAS 4.x and earlier versions in that the org.jboss.Main entry point loads an org.jboss.system.server.Server implementation. In JBossAS 4.x this was a JMX based microkernel. In JBossAS 5 this is a JBoss Microcontainer.
+ </para>
+ <indexterm><primary>JBossAS</primary><secondary>Server interface implementation</secondary></indexterm>
+ <para>The default JBossAS 5 org.jboss.system.server.Server implementation is org.jboss.bootstrap.microcontainer.ServerImpl. This implementation is an extension of the kernel basic bootstrap that boots the MC from the bootstrap beans declared in {jboss.server.config.url}/bootstrap.xml descriptors using a BasicXMLDeployer. In addition, the ServerImpl registers install callbacks for any beans that implement the org.jboss.bootstrap.spi.Bootstrap interface. The bootstrap/profile*.xml configurations include a ProfileServiceBootstrap bean that implements the Bootstrap interface.
+ </para>
+ <indexterm><primary>ProfileService</primary><secondary>bootstrap</secondary></indexterm>
+ <para>The org.jboss.system.server.profileservice.ProfileServiceBootstrap is an implementation of the org.jboss.bootstrap.spi.Bootstrap interface that loads the deployments associated with the current profile. The {profile-name} is the name of the profile being loaded and corresponds to the server -c command line argument. The default {profile-name} is "default". The deployers, deploy</para>
+ </sect1>
+ <sect1 id="Architecture_Hotdeployment">
+ <title>Hot Deployment</title>
+ <indexterm><primary>Hot deployment</primary><secondary>implementation</secondary></indexterm>
+ <para>Hot deployment in JBossAS 5 is controlled by the Profile implementations associated with the ProfileService. The HDScanner bean deployed via the deploy/hdscanner-jboss-beans.xml MC deployment, queries the profile service for changes in application directory contents and redeploys updated content, undeploys removed content, and adds new deployment content to the current profile via the ProfileService. </para>
+ <indexterm><primary>Hot deployment</primary><secondary>disabling</secondary></indexterm>
+ <para>Disabling hot deployment simply entails removing the hdscanner-jboss-beans.xml deployment.</para>
+ </sect1>
+
</chapter>
\ No newline at end of file
Modified: projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Microcontainer.xml
===================================================================
--- projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Microcontainer.xml 2008-12-18 00:59:03 UTC (rev 82352)
+++ projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Microcontainer.xml 2008-12-18 01:03:02 UTC (rev 82353)
@@ -3,13 +3,14 @@
]>
<chapter><title>Microcontainer</title>
-
-<para>JBoss Application Server 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 you are free to remove any services that you don't need simply by changing the configuration. You can even use the microcontainer to do this in other environments such as Tomcat and GlassFish since you can plug 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>
+<indexterm><primary>MC</primary><see>JBoss Microcontainer</see></indexterm>
+<para>JBossAS 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 you are free to remove any services that you don't need simply by changing the configuration. You can even use the microcontainer to do this in other environments such as Tomcat and GlassFish since you can plug 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>In common 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. Finally 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>
+ <indexterm><primary>JBoss Microcontainer</primary><secondary>project modules</secondary></indexterm>
<para>
This section introduces the various Microcontainer modules. The figure below gives an overview of the modules.
@@ -19,7 +20,7 @@
<imagedata fileref="images/microcontainer.png"/>
</imageobject>
</inlinemediaobject>
-
+
<itemizedlist>
<listitem>
<para>
@@ -28,6 +29,11 @@
</listitem>
<listitem>
<para>
+ <literal>classloader</literal> new peer classloader model, prepared to handle OSGi bundle model.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
The <literal>container</literal> module contains: reflection, the integration point for manipulating class information at runtime, e.g. overriding annotations or obtaining an aop instance advisor. joinpoint, the joinpoint model including the join point factory. classadaptor, the integration and configuration spi. metadata, base metadata types and repository
</para>
</listitem>
@@ -58,65 +64,46 @@
</listitem>
<listitem>
<para>
+ <literal>guice-int</literal> contains the integration classes for guice.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
<literal>osgi-int</literal> contains the integration classes that adapt the OSGi model onto the Microcontainer.
</para>
</listitem>
<listitem>
+ <para><literal>reliance-identity</literal> define identity as a MC POJO service</para>
+ </listitem>
+ <listitem>
+ <para><literal>reliance-rules</literal> define your dependencies with Drools</para>
+ </listitem>
+ <listitem>
+ <para><literal>reliance-jbpm</literal> define your dependencies with jBPM</para>
+ </listitem>
+ <listitem>
<para>
<literal>spring-int</literal> contains the integration classes that adapt the spring model onto the Microcontainer.
</para>
</listitem>
</itemizedlist>
-
</para>
</section>
<section><title>Configuration</title>
- <para>To configure your microcontainer the you can use the <emphasis>JBOSS_HOME/server/<server_configuration>/conf/bootstrap-beans.xml</emphasis> and <emphasis>JBOSS_HOME/server/<server_configuration>/conf/bootstrap-repo-beans.xml</emphasis> files where <emphasis><server_configuration></emphasis> represents the <emphasis>all</emphasis>, <emphasis>default</emphasis> or <emphasis>minimal</emphasis> JBoss AS configurations. The configuration files have comments to guide you on the specific configurations available as illustrated by the example below.
+ <para>To configure the microcontainer bootstrap the you can use the <emphasis>JBOSS_HOME/server/<server_configuration>/conf/bootstrap.xml</emphasis> and <emphasis>JBOSS_HOME/server/<server_configuration>/conf/bootstrap/*.xml</emphasis> 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 bootstrap.xml simply references MC deployment descriptors that should be loaded in the indicated order. The current default profile bootstrap.xml references are:
</para>
-<programlisting role="XML">
- <deployment xmlns="urn:jboss:bean-deployer:2.0">
+ <itemizedlist>
+ <listitem><para>vfs.xml - JBoss VFS caching beans</para></listitem>
+ <listitem><para>classloader.xml - the root class loading beans for the peer class loading model</para></listitem>
+ <listitem><para>aop.xml - JBoss AOP integration and AspectManager beans</para></listitem>
+ <listitem><para>jmx.xml - JBoss JMX kernel initialization</para></listitem>
+ <listitem><para>deployers.xml - Core deployers for -jboss-beans.xml and -service.xml</para></listitem>
+ <listitem><para>bindings.xml - Rewrite of the ServiceBindingManager as a POJO bean</para></listitem>
+ <listitem><para>profile-repository.xml - full featured repository based profile service referenced by bootstrap.xml</para></listitem>
- <!-- All beans use the bootstrap classloader -->
- <classloader><inject bean="BootstrapClassLoader"/></classloader>
-
- <!-- TODO Should split this file up and use the new classloader -->
- <bean name="BootstrapClassLoader" class="org.jboss.system.NoAnnotationURLClassLoader">
- <classloader><null/></classloader>
- <constructor factoryClass="org.jboss.system.NoAnnotationURLClassLoader" factoryMethod="createClassLoader">
- <parameter>
-.....
-......
-<bean name="ProfileServiceBootstrap" class="org.jboss.system.server.profileservice.ProfileServiceBootstrap">
-<property name="kernel"><inject bean="jboss.kernel:service=Kernel"/></property>
-</bean>
+ </itemizedlist>
-<!-- The legacy JMX kernel -->
-<bean name="JMXKernel" class="org.jboss.system.server.jmx.JMXKernel">
-<property name="kernel"><inject bean="jboss.kernel:service=Kernel"/></property>
- <property name="serverImpl"><inject bean="JBossServer"/></property>
- <property name="oldClassLoader">false</property>
-</bean>
-....(content truncated)
-......
-
- <!-- The ManagedDeploymentCreator implementation -->
- <bean name="ManagedDeploymentCreator" class="org.jboss.deployers.plugins.managed.DefaultManagedDeploymentCreator" />
-
- <!-- The holder for deployers that determine structure -->
- <bean name="StructuralDeployers" class="org.jboss.deployers.vfs.plugins.structure.VFSStructuralDeployersImpl">
- <property name="structureBuilder">
- <!-- The consolidator of the structure information -->
- <bean name="StructureBuilder" class="org.jboss.deployers.vfs.plugins.structure.VFSStructureBuilder"/>
- </property>
- <!-- Accept any implementor of structure deployer -->
- <incallback method="addDeployer"/>
- <uncallback method="removeDeployer"/>
-</bean>
-...(content truncated)
-...
-</programlisting>
-
<para>The main beans are:
<itemizedlist>
<listitem>
More information about the jboss-cvs-commits
mailing list