[jboss-cvs] JBossAS SVN: r68353 - trunk/build/docs.

Mon Dec 17 18:50:12 EST 2007

Author: dimitris at jboss.org
Date: 2007-12-17 18:50:12 -0500 (Mon, 17 Dec 2007)
New Revision: 68353

Modified:
   trunk/build/docs/readme.html
Log:
some more notes.

Modified: trunk/build/docs/readme.html
===================================================================

--- trunk/build/docs/readme.html	2007-12-17 22:47:04 UTC (rev 68352)
+++ trunk/build/docs/readme.html	2007-12-17 23:50:12 UTC (rev 68353)
@@ -93,8 +93,8 @@
 </ul><p>JBoss 5 includes numerous features and bug fixes,
 many of them carried over upstream from the 4.x codebase. See the <a href="#Details">Detailed Release Notes</a> section for
 the full details.</p>
-<h2><a name="Compatibility">Compatibility Issues</a></h2>
-<h2><a name="Configuration">Configuration Issues</a></h2>
+<h2><a name="Compatibility">Compatibility Issues</a></h2><ul><li>JBossAS 5 runs under Java 5 but there is an ongoing task to make it run safely under Java 6, too (<a href="http://jira.jboss.com/jira/browse/JBAS-5031">JBAS-5031</a>). If using a Sun Java 6 runtime, you may want to set&nbsp; <span style="font-family: monospace;">-Dsun.lang.ClassLoader.allowArraySyntax=true</span>, as described in <a href="http://jira.jboss.com/jira/browse/JBAS-4491">JBAS-4491</a>.</li><li>If using proprietary JBoss/EJB3 annotations, those&nbsp;have moved into the <span style="font-family: monospace;">org.jboss.ejb3.annotation </span>package, <a href="http://jira.jboss.com/jira/browse/EJBTHREE-1099">EJBTHREE-1099</a>.</li><li>Work on EJB3 Extended Persistence Context support is not completed, <a href="http://jira.jboss.com/jira/browse/EJBTHREE-1026">EJBTHREE-1026</a>.</li><li>Interoperating with previous JBoss EJB3 implementations may present problems due to serialVersionUIDs issues,<a href="ht!
 tp://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></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
 series with some notable differences:</p>
 <ul> <li>bin - start scripts and run.jar</li> <li>client
@@ -114,18 +114,15 @@
 - obsolete cmp config</li> <li>standardjbosscmp-jdbc.xml -
 the same cmp2 config</li> <li>standardjboss.xml - the same
 ejb2 config </li> <li>xmdesc/ - legacy xmbean descriptors</li>
-</ul> <li>deploy/ - the same deploy directory, however <b>hot
-deploy is not currently enabled</b>. Only the jsr88/legacy
-RMIAdaptor to the MainDeployerMBean is supported for hot deployment.</li>
-<li><b>deployers/ - new vdf deployers</b><ul> <li>aop-mc-int-aspect-beans.xml
-- aspect/mc integration beans</li> <li>client-deployer-beans.xml
-- ee14 client deployer</li> <li>ear-deployer-beans.xml -
-ear deployers</li> <li>ejb3.deployer/ - ejb3 deployers</li>
-<li>ejb-deployer-beans.xml - ejb2 deployers</li> <li>boss-aop-jboss5.deployer/
-- aspect deployer</li> <li>jbossweb.deployer/ - war
-deployers</li> <li>jca-deployers-beans.xml - jca deployers</li>
-</ul></li> <li>lib/ - the same static library jars</li>
-</ul></li></ul></li></ul><!-- ======================================================= --><h2><a name="Libraries">Library Updates</a></h2>
+</ul> <li>deploy/ - the same deploy directory.</li>
+<li><b>deployers/ - new vdf deployers</b><ul> <li>bsh-deployer - beanshell deployer</li><li>ejb3.deployer - ejb3 deployers</li><li>jboss-aop-jboss5.deployer - aspect deployer</li><li>jboss-jca.deployer - JCA deployers</li><li>jbossweb.deployer - war deployers</li><li>jbossws.deployer - web services deployers</li><li>ear-deployer-beans.xml - ear deployers</li><li>ejb-deployer-beans.xml - ejb deployers</li><li>metadata-beans.xml - metadata handlers</li><li>security-deployer-beans.xml - security deployers</li></ul></li> <li>lib/ - the same static library jars</li>
+</ul></li></ul></li></ul>Clustering related changes. Check out the&nbsp;<a href="http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossAS5ClusteringChanges">Wiki</a> for more info.<ul><li>The clustering configurations have been organized in the deploy dir in a new <span style="font-family: monospace;">cluster</span> subfolder (<a class="external" href="http://jira.jboss.com/jira/browse/JBAS-4709">JBAS-4709</a>).</li><li>A separate cache is now used for Clustered SSO (<a class="external" href="http://jira.jboss.com/jira/browse/JBAS-4676">JBAS-4676</a>).</li><li>Per webapp configuration of useJK, snapshot mode and snapshot interval (<a class="external" href="http://jira.jboss.com/jira/browse/JBAS-3460">JBAS-3460</a>).&nbsp;Default for useJK is whether jvmRoute is set (<a class="external" href="http://jira.jboss.com/jira/browse/JBAS-4961">JBAS-4961</a>).</li><li>Setting of default clustering metadata removed from the Web Deployer (<a class="external" href="http://jira.jboss.com/jira/b!
 rowse/JBAS-4967">JBAS-4967</a>). </li></ul>Known issues<br><ul><li>Hot
+deployment is enabled, however undeployment&nbsp;on Windows, by
+removing files from the ./deploy directory&nbsp; is problematics due to
+jar files being locked, <a href="http://jira.jboss.com/jira/browse/JBAS-4310">JBAS-4310</a>.</li><li>The Farm service is removed. Distributed deployments will eventually be handled by the AS 5 Profile Service, 
+with the Profile Service (or JBoss ON) coordinating deployments across the 
+cluster from a centralized repository. The Farm Service's function of 
+replicating deployment archives between file systems will not be maintained.</li><li>The JSR77 view of the server is not implemented yet.</li></ul><h2><a name="Libraries">Library Updates</a></h2>
 For a full list of the JBoss and thirdparty libraries used
 with JBoss AS 5.0.0.Beta3 see &nbsp;<a href="http://anonsvn.jboss.org/repos/jbossas/tags/JBoss_5_0_0_Beta3/build/build-thirdparty.xml">build-thirdparty.xml.</a>
 <h3>JBossAS 5.0.0.Beta3</h3>JBoss Library Updates


