[jboss-cvs] JBossAS SVN: r94818 - 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
Wed Oct 14 00:53:55 EDT 2009
Author: laubai
Date: 2009-10-14 00:53:55 -0400 (Wed, 14 Oct 2009)
New Revision: 94818
Modified:
projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US/Introduction.xml
projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US/Microcontainer.xml
Log:
Buildable and bereft of VDF references.
Modified: projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US/Introduction.xml
===================================================================
--- projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US/Introduction.xml 2009-10-14 04:53:09 UTC (rev 94817)
+++ projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US/Introduction.xml 2009-10-14 04:53:55 UTC (rev 94818)
@@ -45,11 +45,11 @@
Oriented Programming framework (JBoss AOP). JBoss AOP is discussed in <xref linkend="jboss_aop"/> Support for JMX in JBoss Enterprise Application Platform 5 remains strong and MBean services written against the old Microkernel are expected to work.
</para>
- <para>
+ <!--<para>
JBoss Enterprise Application Platform 5 is designed around the advanced concept of a Virtual Deployment
Framework (VDF).
The JBoss Enterprise Application Platform 5 Virtual Deployment Framework (VDF) takes the aspect oriented design of many of the earlier JBoss containers and applies it to the deployment layer. It is also based on the POJO microntainer rather than JMX as in previous releases. More information about the Virtual Deployment Framework (VDF) can be found in <xref linkend="virtual_deployment_framework"/>.
- </para>
+ </para>-->
<para>
A sample Java EE 5 application that can be run on top of JBoss Enterprise Application Platform 5.0.0.GA and above which demonstrates many interesting technologies is the Seam Booking Application available with this distribution. This example application makes use of the following technologies running on JBoss Enterprise Application Platform 5:</para>
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-10-14 04:53:09 UTC (rev 94817)
+++ projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US/Microcontainer.xml 2009-10-14 04:53:55 UTC (rev 94818)
@@ -2,16 +2,18 @@
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
]>
-<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
+<chapter id="microcontainer">
+ <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.
- Since JBoss Microcontainer is very lightweight and deals with POJOs, it can also be used to deploy
+ 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.
As with other lightweight containers, JBoss Microcontainer uses dependency injection to wire
@@ -21,19 +23,19 @@
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>
+<section id="microcontainer.overview">
+ <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.
-
</para>
- <inlinemediaobject>
+ <mediaobject>
<imageobject>
<imagedata fileref="images/microcontainer.png"/>
</imageobject>
- </inlinemediaobject>
+ </mediaobject>
<itemizedlist>
<listitem>
@@ -101,7 +103,8 @@
</itemizedlist>
</section>
-<section><title>Configuration</title>
+<section id="microcontainer.config">
+ <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>, <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>
@@ -128,7 +131,7 @@
</para>
</listitem>
<listitem>
- <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><emphasis>MainDeployer</emphasis> : An update of the JMX based MainDeployer from earlier versions to one based on the Microcontainer and the 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>
@@ -160,7 +163,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>*-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 Virtual Development Framework-->. 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>
@@ -192,11 +195,8 @@
</para>
</section>
-
-
-
-<section><title>References</title>
- <para>More information on the JBoss Microcontainer project can be obtained from <ulink url="http://www.jboss.org/jbossmc/"/>. </para>
+<section id="microcontainer.ref">
+ <title>References</title>
+ <para>More information on the JBoss Microcontainer project can be obtained from <ulink url="http://www.jboss.org/jbossmc/">http://www.jboss.org/jbossmc/"</ulink>.</para>
</section>
-
</chapter>
More information about the jboss-cvs-commits
mailing list