[jboss-cvs] JBossAS SVN: r78601 - tags/JBoss_5_0_0_CR2/build/docs.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Tue Sep 16 16:47:38 EDT 2008
Author: dimitris at jboss.org
Date: 2008-09-16 16:47:38 -0400 (Tue, 16 Sep 2008)
New Revision: 78601
Modified:
tags/JBoss_5_0_0_CR2/build/docs/readme.html
Log:
JBAS-5962, done.
Modified: tags/JBoss_5_0_0_CR2/build/docs/readme.html
===================================================================
--- tags/JBoss_5_0_0_CR2/build/docs/readme.html 2008-09-16 20:27:56 UTC (rev 78600)
+++ tags/JBoss_5_0_0_CR2/build/docs/readme.html 2008-09-16 20:47:38 UTC (rev 78601)
@@ -11,9 +11,9 @@
EE™</b>
5 codebase and the first JBossAS release that fully complies with the
Java EE 5 conformance testing
-certification requirements! Obviously, this is a big milestone in the
+certification requirements! This is an important milestone in the
development of JBossAS as we will have more time now to spend on
-developer productivety features and server manageability improvements.</p><p>A common theme for JBossAS 5 is the breaking out of internal subsystems into stand-alone projects
+developer productivity features and server manageability improvements.</p><p>A common theme for JBossAS 5 is the breaking out of internal subsystems into stand-alone projects
and the introduction of SPIs throughout the server codebase. Those changes should not affect directly the end
user but they are an important part of the JBoss strategy for making
available the various EE services as independent projects, so that they
@@ -97,7 +97,7 @@
without active user management of either replication or persistency
aspects.</li> <li><a href="http://labs.jboss.com/portal/jbossws">JBossWS</a>
is the web services stack for JBoss 5 providing Java EE compatible web
-services, JAXWS-2.0.</li> <li><a href="http://www.jboss.com/products/transactions">JBoss
+services, JAX-WS-2.0.</li> <li><a href="http://www.jboss.com/products/transactions">JBoss
Transactions</a> is the default transaction manager for JBoss 5.
JBoss Transactions is founded on industry proven technology and 18 year
history as a leader in distributed transactions, and is one of the most
@@ -127,7 +127,7 @@
noted however that the Java 6 compiled distribution of JBoss AS 5 is
still in experimental stage.</li></ul>Other compatibility issues:<br><ul><li>All
the *-beans.xml configuration files have been renamed to
-*-jboss-beans.xml to avoid conflicts with spring configuration files.</li><li>JBoss
+*-jboss-beans.xml to avoid conflicts with spring configuration files.</li><li>For mod_cluster integration you will have to use the workaround described in <a href="https://jira.jboss.org/jira/browse/JBAS-5966">JBAS-5966</a> until the tomcat service mbean descriptor is converted to an MC bean descriptor.</li><li>JBoss
VFS provides a set of different switches to control it's internal
behavior. JBoss AS sets <span style="font-family: monospace;">jboss.vfs.forceCopy=true</span>
by default. To see all the provided VFS flags check out the code of the
@@ -155,7 +155,7 @@
serialVersionUIDs issues,<a href="http://jira.jboss.com/jira/browse/EJBTHREE-1118">
EJBTHREE-1118</a>.</li><li>Use of JBoss
Cache 2.x. JBC 2.x has a significantly different API from the 1.x
-releases used in JBoss AS 4.x and 3.2.x.</li><li>@EJB injections should now work from servlets, JBAS-5646.</li><li>The ClassPathExtension MBean has been replaced with a VFS classloader definition, see JBAS-5446.</li></ul>For strict JavaEE compatibiliity compliance you can:<br><ul><li>Enable call-by-value in deployers/ear-deployer-jboss-beans.xml<br><property name="callByValue">true</property> </li><li>Enable call-by-value for "jboss:service=Naming" in conf/jboss-service.xml<br><attribute name="CallByValue">true</attribute></li><li>Set the following system property in your startup script<br>-Dorg.apache.catalina.STRICT_SERVLET_COMPLIANCE=true</li></ul><h2><a name="Configuration">Configuration Issues</a></h2>
+releases used in JBoss AS 4.x and 3.2.x.</li><li>@EJB injections should now work from servlets, JBAS-5646.</li><li>The ClassPathExtension MBean has been replaced with a VFS classloader definition, see JBAS-5446.</li></ul>For strict JavaEE compatibility compliance you can:<br><ul><li>Enable call-by-value in deployers/ear-deployer-jboss-beans.xml<br><property name="callByValue">true</property> </li><li>Enable call-by-value for "jboss:service=Naming" in conf/jboss-service.xml<br><attribute name="CallByValue">true</attribute></li><li>Set the following system property in your startup script<br>-Dorg.apache.catalina.STRICT_SERVLET_COMPLIANCE=true</li></ul><h2><a name="Configuration">Configuration Issues</a></h2>
<p>This section lists changes that could affect the server
configuration.</p><p>The directory structure of JBoss 5
resembles that of the 4.x
More information about the jboss-cvs-commits
mailing list