[jboss-cvs] JBossAS SVN: r100201 - projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Mon Feb 1 02:33:38 EST 2010
Author: laubai
Date: 2010-02-01 02:33:38 -0500 (Mon, 01 Feb 2010)
New Revision: 100201
Modified:
projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Introduction.xml
projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/JGroups.xml
projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Microcontainer.xml
Log:
Edited Microcontainer.xml
Modified: projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Introduction.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Introduction.xml 2010-02-01 07:21:19 UTC (rev 100200)
+++ projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Introduction.xml 2010-02-01 07:33:38 UTC (rev 100201)
@@ -6,10 +6,10 @@
<title>Introduction</title>
<para>
<indexterm><primary>JBoss Enterprise Web Platform</primary><secondary>microcontainer</secondary></indexterm>
- JBoss Enterprise Web Platform 5 is built on top of the new JBoss Microcontainer.
- The JBoss Microcontainer is a lightweight container that supports direct deployment, configuration and lifecycle of plain old Java objects (POJOs).
- <indexterm><primary>JBoss Enterprise Web Platform</primary><secondary>JMX Microkernel</secondary></indexterm>
- The JBoss Microcontainer project is standalone and replaces the JBoss JMX Microkernel used in the 4.x JBoss Enterprise Web Platforms.
+ JBoss Enterprise Web Platform is built on top of the new JBoss Microcontainer.
+ The JBoss Microcontainer is a lightweight container that supports direct deployment, configuration and lifecycle of plain old Java objects (POJOs). JBoss Microcontainer replaces the JBoss JMX Microkernel.
+ <!--<indexterm><primary>JBoss Enterprise Web Platform</primary><secondary>JMX Microkernel</secondary></indexterm>
+ The JBoss Microcontainer project is standalone and replaces the JBoss JMX Microkernel used in the 4.x JBoss Enterprise Web Platforms.-->
<!-- Project goals include: -->
</para>
<!-- <para>
@@ -42,7 +42,7 @@
</itemizedlist> -->
<para>
The JBoss Microcontainer integrates nicely with the JBoss Aspect
- Oriented Programming framework (JBoss AOP). JBoss AOP is discussed in <xref linkend="jboss_aop"/> Support for JMX in JBoss Enterprise Web Platform 5 remains strong and MBean services written against the old Microkernel are expected to work.
+ Oriented Programming framework (JBoss AOP). JBoss AOP is discussed in <xref linkend="jboss_aop"/>. Support for JMX in JBoss Enterprise Web Platform remains strong and MBean services written against the old Microkernel are expected to work.
</para>
<!--<para>
@@ -52,7 +52,7 @@
</para>-->
<para>
- A sample Java EE 5 application that can be run on top of JBoss Enterprise Web 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 Web Platform 5:</para>
+ The Seam Booking sample application is Java EE 5 compliant. It demonstrates many of the technologies available on the Enterprise Web Platform, such as:</para>
<itemizedlist>
<listitem>
@@ -104,11 +104,11 @@
JBoss EJB3 included with JBoss Enterprise Web Platform 5 provides the implementation of the latest revision of the Enterprise Java Beans (EJB) specification. EJB 3.0 is a deep overhaul and simplification of the EJB specification. EJB 3.0's goals are to simplify development, facilitate a test driven approach, and focus more on writing plain old java objects (POJOs) rather than coding against complex EJB APIs.
</para>
</listitem>
- <listitem>
+<!-- <listitem>
<para>
JBoss Messaging is a high performance JMS provider included in JBoss Enterprise Web Platform 5 as the default messaging provider. It is also the backbone of the JBoss ESB infrastructure. JBoss Messaging is a complete rewrite of JBossMQ, which is the default JMS provider for JBoss Enterprise Web Platform 4.2.
</para>
- </listitem>
+ </listitem>-->
<listitem>
<para>
JBoss Cache comes in two flavors: a traditional tree-structured node-based cache, and a PojoCache, an in-memory, transactional, and replicated cache system that allows users to operate on simple POJOs transparently without active user management of either replication or persistency aspects.
@@ -116,7 +116,7 @@
</listitem>
<listitem>
<para>
- JBossWS 3.x is the web services stack for JBoss Enterprise Web Platform 5 providing Java EE compatible web services, JAXWS-2.x.
+ JBoss Web Services 3.x is the web services stack for JBoss Enterprise Web Platform, providing Java EE compatible web services, JAXWS-2.x, etc.
</para>
</listitem>
<listitem>
@@ -159,12 +159,12 @@
</listitem>
<listitem>
<para>
- Complex web applications with JSPs/Servlets, SEAM, Enterprise Java Beans (EJB), Java Messaging (JMS), caching etc.
+ Complex web applications with JSPs/Servlets, Seam, Enterprise Java Beans (EJB), Java Messaging (JMS), caching, etc.
</para>
</listitem>
<listitem>
<para>
- Cross application middleware (JMS, Corba, JMX etc).
+ Cross application middleware (JMS, Corba, JMX, etc.)
</para>
</listitem>
</itemizedlist>
@@ -309,4 +309,3 @@
</section> -->
</chapter>
-
Modified: projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/JGroups.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/JGroups.xml 2010-02-01 07:21:19 UTC (rev 100200)
+++ projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/JGroups.xml 2010-02-01 07:33:38 UTC (rev 100201)
@@ -12,22 +12,22 @@
<orderedlist>
<listitem>
- <para>Group creation and deletion. Group members can be spread across LANs or WANs </para>
+ <para>Group creation and deletion — group members can be spread across LANs or WANs</para>
</listitem>
<listitem>
- <para>Joining and leaving of groups </para>
+ <para>Joining and leaving of groups</para>
</listitem>
<listitem>
- <para>Membership detection and notification about joined/left/crashed members </para>
+ <para>Membership detection and notification about joined/left/crashed members</para>
</listitem>
<listitem>
- <para>Detection and removal of crashed members </para>
+ <para>Detection and removal of crashed members</para>
</listitem>
<listitem>
- <para>Sending and receiving of member-to-group messages (point-to-multipoint) </para>
+ <para>Sending and receiving of member-to-group messages (point-to-multipoint)</para>
</listitem>
<listitem>
- <para>Sending and receiving of member-to-member messages (point-to-point) </para>
+ <para>Sending and receiving of member-to-member messages (point-to-point)</para>
</listitem>
</orderedlist>
@@ -52,7 +52,7 @@
<para>Failure detection: crashed members are excluded from the membership </para>
</listitem>
<listitem>
- <para>Ordering protocols: Atomic (all-or-none message delivery), Fifo, Causal, Total Order (sequencer or token based) </para>
+ <para>Ordering protocols: Atomic (all-or-none message delivery), FIFO, Causal, Total Order (sequencer or token based) </para>
</listitem>
<listitem>
<para>Membership </para>
Modified: projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Microcontainer.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Microcontainer.xml 2010-02-01 07:21:19 UTC (rev 100200)
+++ projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Microcontainer.xml 2010-02-01 07:33:38 UTC (rev 100201)
@@ -6,16 +6,16 @@
<title>Microcontainer</title>
<!--<indexterm><primary>MC</primary><see>JBoss Microcontainer</see></indexterm>-->
- <para>JBoss Enterprise Web Platform 5.0 uses the Microcontainer to integrate enterprise services
+ <para>JBoss Enterprise Web Platform 5.0 uses JBoss 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
+ 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
+ the service deployment phase.--></para>
+ <para>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.
+ 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
@@ -45,7 +45,7 @@
</listitem>
<listitem>
<para>
- <literal>Integr.</literal> represents the <literal>aop-mc-int</literal> module, which handles integration between the JBoss AOP and JBoss Microcontainer.
+ <literal>Integr.</literal> represents the <classname>aop-mc-int</classname> module, which handles integration between the JBoss AOP and JBoss Microcontainer.
</para>
</listitem>
<listitem>
@@ -55,7 +55,7 @@
</listitem>
<listitem>
<para>
- <literal>Reliance</literal> represents two modules: <literal>Drools-int</literal> and <literal>jBPM-int</literal>. These modules define Drools dependencies.
+ <literal>Reliance</literal> represents two modules: <classname>Drools-int</classname> and <classname>jBPM-int</classname>. These modules define JBoss Rules dependencies.
</para>
</listitem>
<listitem>
@@ -105,95 +105,100 @@
<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>To configure the Microcontainer bootstrap you can use the <filename>$JBOSS_HOME/server/$PROFILE/conf/bootstrap.xml</filename> and <filename>$JBOSS_HOME/server/$PROFILE/conf/bootstrap/*.xml</filename> files where <literal>$PROFILE</literal> represents the name of the server profile; either <literal>production</literal> or <literal>default</literal>. The <filename>bootstrap.xml</filename> simply references Microcontainer deployment descriptors that should be loaded in the indicated order. The current <literal>default</literal> 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>profile.xml</filename> - full featured repository based profile service referenced by <filename>bootstrap.xml</filename></para></listitem>
+ <variablelist>
+ <varlistentry>
+ <term><filename>logging.xml</filename></term>
+ <listitem><para>Logging manager and bridge configuration.</para></listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><filename>vfs.xml</filename></term>
+ <listitem><para>JBoss VFS caching beans.</para></listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><filename>classloader.xml</filename></term>
+ <listitem><para>The root class loading beans for the peer class loading model.</para></listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><filename>aop.xml</filename></term>
+ <listitem><para>JBoss AOP integration and AspectManager beans.</para></listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><filename>jmx.xml</filename></term>
+ <listitem><para>JBoss JMX kernel initialization.</para></listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><filename>deployers.xml</filename></term>
+ <listitem><para>Core deployers for <filename>-jboss-beans.xml</filename> and <filename>-service.xml</filename>.</para></listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><filename>profile.xml</filename></term>
+ <listitem><para>Full featured repository based profile service referenced by <filename>bootstrap.xml</filename></para></listitem>
+ </varlistentry>
+ </variablelist>
<!--<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>, <filename>server/name/deployers</filename> and <filename>server/name/deploy</filename> to load deployments.
- </para>
- </listitem>
- <listitem>
- <para><emphasis>AspectManager</emphasis> : the AOP aspects
- </para>
- </listitem>
- <listitem>
- <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>
- <para><emphasis>ServiceClassLoaderDeployer</emphasis> : Manages the class loading aspect of deployment.
- </para>
- </listitem>
- <listitem>
- <para><emphasis>JARDeployer</emphasis> : This bean is a structural deployment aspect which handles the legacy nested deployment behavior of adding non-deployable jars to the current deployment classpath.
- </para>
- </listitem>
- <listitem>
- <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>
- </listitem>
- <listitem>
- <para><emphasis>BeanDeployer</emphasis> : this bean translates <filename>*-jboss-beans.xml</filename> into <classname>KernelDeployment</classname> for the descriptor beans.
- </para>
- </listitem>
- <listitem>
- <para><emphasis>KernelDeploymentDeployer</emphasis> : Translates a <classname>KernelDeployment</classname> into the constituent <classname>BeanMetaData</classname> instances for the kernel beans.
- </para>
- </listitem>
- <listitem>
- <para><emphasis>BeanMetaDataDeployer</emphasis> : Creates the kernel beans from the deployment <classname>BeanMetaData</classname>.
- </para>
- </listitem>
- <listitem>
- <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>
- <para><emphasis>ServiceDeploymentDeployer</emphasis> : Translates the <classname>ServiceDeployment</classname> POJO into the constituent <classname>ServiceMetaData</classname> that represent the various mbeans.
- </para>
- </listitem>
- <listitem>
- <para><emphasis>ServiceDeployer</emphasis> : creates the mbean services from deployment <classname>ServiceMetaData</classname> instances.
- </para>
- </listitem>
- <listitem>
- <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>
- <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>
- <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>
- </listitem>
- </itemizedlist>
+<para>The main beans are:</para>
+ <variablelist>
+ <varlistentry>
+ <term><classname>ProfileService</classname></term>
+ <listitem><para>Loads the deployments associated with the specified server profile. Constantly examines <filename>server/$PROFILE/conf/jboss-service.xml</filename>, <filename>server/$PROFILE/deployers</filename> and <filename>server/$PROFILE/deploy</filename> for deployments.</para></listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><classname>AspectManager</classname></term>
+ <listitem><para>AOP aspects.</para></listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><classname>MainDeployer</classname></term>
+ <listitem><para>Deployer aspects are registered with the <classname>MainDeployer</classname> as an ordered list via an injection of the <varname>deployers</varname> property.</para></listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><classname>ServiceClassLoaderDeployer</classname></term>
+ <listitem><para>Manages the class loading aspect of deployment.</para></listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><classname>JARDeployer</classname></term>
+ <listitem><para>A structural deployment aspect which handles the legacy nested deployment behavior of adding non-deployable JARs to the current deployment classpath.</para></listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><classname>FileStructure</classname></term>
+ <listitem><para>A structural deployment aspect which recognizes common deployment file types by suffix, as specified by <classname>FileManager</classname>.</para></listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><classname>AspectDeployer</classname></term>
+ <listitem><para>Handles AOP descriptor deployments.</para></listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><classname>BeanDeployer</classname></term>
+ <listitem><para>Translates <filename>*-jboss-beans.xml</filename> into <classname>KernelDeployment</classname> for the descriptor beans.</para></listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><classname>KernelDeploymentDeployer</classname></term>
+ <listitem><para>Translates a <classname>KernelDeployment</classname> into the constituent <classname>BeanMetaData</classname> instances for the kernel beans.</para></listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><classname>SARDeployer</classname></term>
+ <listitem><para>Handles legacy <filename>*-service.xml</filename> MBean descriptors and maps them as <classname>ServiceDeployment</classname> POJOs.</para></listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><classname>ServiceDeploymentDeployer</classname></term>
+ <listitem><para>Translates the <classname>ServiceDeployment</classname> POJO into the constituent <classname>ServiceMetaData</classname> that represent the various MBeans.</para></listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><classname>ServiceDeployer</classname></term>
+ <listitem><para>Creates the MBean services from deployment <classname>ServiceMetaData</classname> instances.</para></listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><classname>JMXKernel</classname></term>
+ <listitem><para>Manages JMX kernel and <classname>MBeanServer</classname> instantiation in the JBoss domain. It is used by <classname>SARDeployer</classname> and will be used to expose kernel beans via JMX in the future.</para></listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><classname>HDScanner</classname></term>
+ <listitem><para>Queries the profile service for changes to the <filename>deploy</filename> directory contents. It then redeploys updated content, undeploys removed content, and adds new deployment content to the profile service.</para></listitem>
+ </varlistentry>
-</para>
-
</section>
<section id="microcontainer.ref">
<title>References</title>
More information about the jboss-cvs-commits
mailing list