[jboss-cvs] JBossAS SVN: r98069 - 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 Dec 21 01:38:09 EST 2009
Author: laubai
Date: 2009-12-21 01:38:08 -0500 (Mon, 21 Dec 2009)
New Revision: 98069
Modified:
projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Architecture.xml
Log:
Edited Architecture chapter of Admin and Config Guide.
Modified: projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Architecture.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Architecture.xml 2009-12-21 06:07:08 UTC (rev 98068)
+++ projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Architecture.xml 2009-12-21 06:38:08 UTC (rev 98069)
@@ -3,10 +3,10 @@
]>
<chapter id="JBoss_Enterprise_Application_Platform_5_Architecture">
- <title>JBoss Enterprise Application Platform 5 architecture</title>
+ <title>JBoss Enterprise Web Platform 5 Architecture</title>
<para>
- <indexterm><primary>JBoss Enterprise Application Platform</primary><secondary>architecture</secondary></indexterm>
- The following diagram illustrates an overview of the JBoss Enterprise Application Server and its components.
+ <indexterm><primary>JBoss Enterprise Web Platform</primary><secondary>architecture</secondary></indexterm>
+ The following diagram illustrates an overview of the JBoss Enterprise Web Platform and its components.
<inlinemediaobject>
<imageobject>
<imagedata fileref="images/jboss-as-components.png"/>
@@ -15,7 +15,7 @@
</para>
<para>
- The directory structure of JBoss Enterprise Application Platform 5 resembles that of the 4.x series with some notable differences:
+ The directory structure of JBoss Enterprise Web Platform is outlined here:
</para>
<screen>
<![CDATA[-jboss-as - the path to your JBoss Enterprise Application Server.
@@ -29,13 +29,13 @@
for details of the server profiles included in this release.
]]></screen>
<screen>
-<![CDATA[-seam - the path to JBoss SEAM application framework
+<![CDATA[-seam - the path to JBoss Seam application framework
|-- bootstrap
|-- build
- |-- examples - examples demonstrating uses of SEAM's features
+ |-- examples - examples demonstrating uses of Seam's features
|-- extras
|-- lib - library directory
- |-- seam-gen - command-line utility used to generate simple skeletal SEAM code to get your project started
+ |-- seam-gen - command-line utility used to generate simple skeletal Seam code to get your project started
|-- ui -
]]></screen>
@@ -47,22 +47,22 @@
]]></screen>
<section id="Architecture_Server_Bootstrap">
- <title>The JBoss Enterprise Application Platform Bootstrap</title>
- <indexterm><primary>JBoss Enterprise Application Platform</primary><secondary>bootstrap</secondary></indexterm>
- <para>The JBoss Enterprise Application Platform 5 bootstrap is similar to the JBoss Enterprise Application Platform 4.x versions in that the org.jboss.Main entry point loads an org.jboss.system.server.Server implementation. In JBoss Enterprise Application Platform 4.x this was a JMX based microkernel. In JBoss Enterprise Application Platform 5 this is a JBoss Microcontainer.
+ <title>The JBoss Enterprise Web Platform Bootstrap</title>
+ <indexterm><primary>JBoss Enterprise Web Platform</primary><secondary>bootstrap</secondary></indexterm>
+ <para>
+ The <classname>org.jboss.Main</classname> entry point in JBoss Enterprise Web Platform 5 loads an <classname>org.jboss.system.server.Server</classname> implementation. This is a JBoss Microcontainer.
</para>
- <indexterm><primary>JBoss Enterprise Application Platform</primary><secondary>Server interface implementation</secondary></indexterm>
- <para>The default JBoss Enterprise Application Platform 5 <classname>org.jboss.system.server.Server implementation</classname> is <classname>org.jboss.bootstrap.microcontainer.ServerImpl</classname>. This implementation is an extension of the kernel basic bootstrap that boots the MC from the bootstrap beans declared in <filename>{jboss.server.config.url}/bootstrap.xml</filename> descriptors using a <classname>BasicXMLDeployer</classname>. In addition, the <classname>ServerImpl</classname> registers install callbacks for any beans that implement the <classname>org.jboss.bootstrap.spi.Bootstrap</classname> interface. The <filename>bootstrap/profile*.xml</filename> configurations include a <classname>ProfileServiceBootstrap</classname> bean that implements the Bootstrap interface.
+ <indexterm><primary>JBoss Enterprise Web Platform</primary><secondary>Server interface implementation</secondary></indexterm>
+ <para>The default JBoss Enterprise Web Platform 5 <classname>org.jboss.system.server.Server implementation</classname> is <classname>org.jboss.bootstrap.microcontainer.ServerImpl</classname>. This implementation is an extension of the kernel basic bootstrap that boots the MC from the bootstrap beans declared in <filename><![CDATA[<jboss.server.config.url>/bootstrap.xml]]></filename> descriptors using a <classname>BasicXMLDeployer</classname>. In addition, the <classname>ServerImpl</classname> registers install callbacks for any beans that implement the <classname>org.jboss.bootstrap.spi.Bootstrap</classname> interface. The <filename>bootstrap/profile*.xml</filename> configurations include a <classname>ProfileServiceBootstrap</classname> bean that implements the <classname>Bootstrap</classname> interface.
</para>
<indexterm><primary>ProfileService</primary><secondary>bootstrap</secondary></indexterm>
- <para>The <classname>org.jboss.system.server.profileservice.ProfileServiceBootstrap</classname> is an implementation of the <classname>org.jboss.bootstrap.spi.Bootstrap</classname> interface that loads the deployments associated with the current profile. The <emphasis>{profile-name}</emphasis> is the name of the profile being loaded and corresponds to the <code>server -c</code> command line argument. The default <emphasis>{profile-name}</emphasis> is <emphasis>default</emphasis>. The deployers, deploy</para>
+ <para>The <classname>org.jboss.system.server.profileservice.ProfileServiceBootstrap</classname> is an implementation of the <classname>org.jboss.bootstrap.spi.Bootstrap</classname> interface that loads the deployments associated with the current profile. The <literal>$PROFILE</literal> is the name of the server configuration profile being loaded and corresponds to the <code>server -c</code> command line argument. The default <literal>$PROFILE</literal> is <literal>default</literal>.</para>
</section>
<section id="Architecture_Hotdeployment">
<title>Hot Deployment</title>
<indexterm><primary>Hot deployment</primary><secondary>implementation</secondary></indexterm>
- <para>Hot deployment in JBoss Enterprise Application Platform 5 is controlled by the <classname>Profile</classname> implementations associated with the <classname>ProfileService</classname>. The <classname>HDScanner</classname> bean deployed via the <filename>deploy/hdscanner-jboss-beans.xml</filename> 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 <classname>ProfileService</classname>. </para>
+ <para>Hot deployment in JBoss Enterprise Web Platform 5 is controlled by the <classname>Profile</classname> implementations associated with the <classname>ProfileService</classname>. The <classname>HDScanner</classname> bean deployed via the <filename>deploy/hdscanner-jboss-beans.xml</filename> 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 <classname>ProfileService</classname>. </para>
<indexterm><primary>Hot deployment</primary><secondary>disabling</secondary></indexterm>
- <para>Disabling hot deployment is achieved by removing the <filename>hdscanner-jboss-beans.xml</filename> file from deployment.</para>
+ <para>Disabling hot deployment is achieved by removing the <filename>hdscanner-jboss-beans.xml</filename> file from your deployment.</para>
</section>
-
</chapter>
More information about the jboss-cvs-commits
mailing list