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

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

Author: laubai
Date: 2009-09-29 21:11:10 -0400 (Tue, 29 Sep 2009)
New Revision: 94133

Modified:
   projects/docs/enterprise/5.0/Installation_Guide/en-US/Migration.xml
Log:
Corrected XML so that it builds; have not corrected contents yet.

Modified: projects/docs/enterprise/5.0/Installation_Guide/en-US/Migration.xml
===================================================================
--- projects/docs/enterprise/5.0/Installation_Guide/en-US/Migration.xml	2009-09-30 01:10:16 UTC (rev 94132)
+++ projects/docs/enterprise/5.0/Installation_Guide/en-US/Migration.xml	2009-09-30 01:11:10 UTC (rev 94133)
@@ -524,7 +524,7 @@
             <para>
              A reminder that the <filename>rpm</filename> and <filename>zip</filename> distributions of the Enterprise Application Platform are shipped with authentication enabled for the JMX Console, Web Console, JMX Invoker, Administration Console, HTTP Invoker and Profile Service. No user accounts are active by default to assist in preventing default user and password-based attacks.
             </para>
-          </listitem>-->
+          </listitem>
           <listitem>
             <para>
               <filename>shutdown.sh</filename> now accepts a JNDI URL, as follows:
@@ -859,7 +859,7 @@
       Portable Java EE applications running on Enterprise Application Platform 4.x can be deployed to Enterprise Application Platform 5.0 without any changes. However, runtime-specific deployment information may be required when migrating from another vendor's application server to Enterprise Application Platform 5.0.
     </para>
     <para>
-      EAP 5.0 users can take advantage of the simplified packaging and deployment rules defined in the Java EE 5 Platform Specification such as no longer requiring an <filename>application.xml<.filename> file in Enterprise Archives (EARs). Additionally, a default library directory (<filename>lib</filename>) in the root directory of an EAR makes the JARs available to all components packaged within the EAR. If an <filename>application.xml</filename> file is included, the <literal>library-directory</literal> element can be used to specify the location of the <filename>lib</filename> directory.
+      EAP 5.0 users can take advantage of the simplified packaging and deployment rules defined in the Java EE 5 Platform Specification such as no longer requiring an <filename>application.xml</filename> file in Enterprise Archives (EARs). Additionally, a default library directory (<filename>lib</filename>) in the root directory of an EAR makes the JARs available to all components packaged within the EAR. If an <filename>application.xml</filename> file is included, the <literal>library-directory</literal> element can be used to specify the location of the <filename>lib</filename> directory.
     </para>
     <para>
       Enterprise Application Platform 5.0 also introduces a new deployable unit: the <emphasis>MCBeans archive</emphasis>, after JBoss Microcontainer, which typically takes the <filename>.beans</filename> or <filename>.deployer</filename> suffix. MCBeans archives package a POJO deployment in a JAR file with a <filename>META-INF/jboss-beans.xml</filename> descriptor. This format is common in Enterprise Application Platform deployers.
@@ -952,4 +952,5 @@
       </programlisting>
     </section>
   </section>
+</section>
 </chapter>