[jboss-cvs] JBossAS SVN: r95234 - projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US.

[jboss-cvs-commits at lists.jboss.org]

Author: laubai
Date: 2009-10-20 22:09:46 -0400 (Tue, 20 Oct 2009)
New Revision: 95234

Modified:
   projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US/Architecture.xml
   projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US/Clustering_Guide_EJBs.xml
Log:
Removing empty tags for brew build.

Modified: projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US/Architecture.xml
===================================================================
--- projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US/Architecture.xml	2009-10-21 01:58:41 UTC (rev 95233)
+++ projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US/Architecture.xml	2009-10-21 02:09:46 UTC (rev 95234)
@@ -46,7 +46,7 @@
 		|-- resteasy-jaxrs.war
 ]]></screen>
 
-	<sect1 id="Architecture_Server_Bootstrap">
+	<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.
@@ -56,13 +56,13 @@
 		</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>
-	</sect1>
-	<sect1 id="Architecture_Hotdeployment">
+	</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>
 		<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>
-	</sect1>
+	</section>
 	
 </chapter>

Modified: projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US/Clustering_Guide_EJBs.xml
===================================================================
--- projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US/Clustering_Guide_EJBs.xml	2009-10-21 01:58:41 UTC (rev 95233)
+++ projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US/Clustering_Guide_EJBs.xml	2009-10-21 02:09:46 UTC (rev 95234)
@@ -335,15 +335,15 @@
 </bean>      
 ]]></programlisting>
       
-      <simplesect>
+      <formalpara>
         <title>Eviction</title>
         <para>
           The default SFSB cache is configured to support eviction. 
           The EJB3 SFSB container uses the JBoss Cache eviction mechanism to manage SFSB passivation.
           When beans are deployed, the EJB container will programatically add eviction regions to the cache, one region per bean type.
         </para>
-      </simplesect>
-      <simplesect>
+      </formalpara>
+      <formalpara>
         <title>CacheLoader</title>
         <para>
           A JBoss Cache CacheLoader is also configured; again to support SFSB passivation.
@@ -354,13 +354,12 @@
           However, if you change the CacheLoaderConfiguration, be sure that you do not use a shared store, e.g. a single schema in a shared database.
           Each node in the cluster must have its own persistent store, otherwise as nodes independently passivate and activate clustered beans, they will corrupt each other's data.
         </para>
-      </simplesect>
-      <simplesect>
+      </formalpara>
+      <formalpara>
         <title>Buddy Replication</title>
         <para>
           Using buddy replication, state is replicated to a configurable number of backup servers in the cluster (aka buddies), rather than to all servers in the cluster.
           To enable buddy replication, adjust the following properties in the <literal>buddyReplicationConfig</literal> property bean:
-        </para>
         <itemizedlist>
           <listitem>
             <para>
@@ -379,7 +378,8 @@
             </para>
           </listitem>
         </itemizedlist>
-      </simplesect>
+        </para>
+      </formalpara>
     </section>
   </section>