[jboss-cvs] JBossAS SVN: r68376 - trunk/build/docs.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Tue Dec 18 07:34:09 EST 2007
Author: dimitris at jboss.org
Date: 2007-12-18 07:34:09 -0500 (Tue, 18 Dec 2007)
New Revision: 68376
Modified:
trunk/build/docs/readme.html
Log:
more ejb3 notes.
Modified: trunk/build/docs/readme.html
===================================================================
--- trunk/build/docs/readme.html 2007-12-18 11:11:05 UTC (rev 68375)
+++ trunk/build/docs/readme.html 2007-12-18 12:34:09 UTC (rev 68376)
@@ -93,7 +93,13 @@
</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><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 <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 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
+<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 <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 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>. Those are now included in a new artifact, jboss-ejb3-ext-api.jar</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="http://jira.jboss.com/jira/browse/EJBTHREE-1118"> EJBTHREE-1118</a>.</li><li>EJB 2.1 View requirements
+</li><ul><li>Home extending <u>EJBLocalHome</u><a href="http://wiki.jboss.org/wiki/Edit.jsp?page=EJBLocalHome">?</a> or EJBHome
+must be defined
+</li></ul><ul><li>Remote or Local interface must either be defined via @Local/@Remote or via
+return type of "create<METHOD>" methods of the Home
+</li></ul><ul><li>EJB 2.1 Remote/Local interfaces must extend EJBObject/EJBLocalObject</li></ul><li>@Local/@Remote may be used to define either EJB 3.0 View Business Interface, or
+EJB 2.1 View Remote/Local interface </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>
@@ -116,7 +122,10 @@
ejb2 config </li> <li>xmdesc/ - legacy xmbean descriptors</li>
</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 <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>). 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
+</ul></li></ul></li></ul>Clustering related changes. Check out the <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>). 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>EJB3
+configuration is now controlled by
+deployers/ejb3.deployer/META-INF/ejb3-deployers-beans.xml. For more
+details check out this <a href="http://wiki.jboss.org/wiki/Wiki.jsp?page=ToAS5.0.0.Beta3">wiki</a> page.<br><br>Other known issues:<br><ul><li>Hot
deployment is enabled, however undeployment on Windows, by
removing files from the ./deploy directory 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,
@@ -129,7 +138,7 @@
<ul> <li>hibernate, v3.2.4.SP1_CP01</li> <li>hibernate-annotations,
v3.3.1.Beta1</li><li>hibernate-commons-annotations, v3.0.0.GA</li> <li>hibernate-entitymanager, v3.3.2.Beta1</li><li>hibernate-validator, v3.0.0.GA</li>
<li>javassist, v3.6.0.GA</li> <li>jboss-aop, v2.0.0.CR1</li><li>jboss-cache, v2.1.0.CR2</li> <li>jboss-common-core,
-v2.2.2.GA</li> <li>jboss-common-logging, v2.0.2.GA</li><li>jboss-ha, v1.0.0.BETA1</li><li>jboss-integration, v5.0.0.Beta4</li><li>jboss-jaxr, v1.2.0.GA</li><li>jboss-ejb3-cache, v0.11.1</li><li>jboss-ejb3-ext-api, v0.1.2.Beta1</li><li>jboss-ejb3-impl, v0.1.2.Beta1</li><li>jboss-jaspi-api, v1.0-BETA1</li><li>jboss-javaee, v5.0.0.Beta3Update1</li><li>jboss-security-spi, v2.0.2.Beta1</li><li>jbosssx, v2.0.2.beta1</li><li>jbosssx-client, v2.0.2.beta</li><li>jbossts, v4.3.0.BETA2</li><li>jboss-vfs, v2.0.0.Beta6</li><li>jbossws-native50, 2.0.2.GA</li><li>jbossxb, v2.0.0.CR5</li><li>jms-integration-tests, v1.0.1.GA</li><li>messaging, v1.4.0.SP1</li><li>metadata, v1.0.0.Beta4</li><li>microcontainer, v2.0.0.Beta7</li><li>profiler/jvmti, v1.0.0.CR5</li><li>remoting, v2.2.2.SP3</li><li>serialization, v1.0.3.GA</li><li>test, v1.0.4.GA</li><li>jboss-web, v2.1.0.CR11</li><li>jgroups, v2.6.1.GA</li></ul>Thirdparty
+v2.2.3.GA</li> <li>jboss-common-logging, v2.0.2.GA</li><li>jboss-ha, v1.0.0.BETA1</li><li>jboss-integration, v5.0.0.Beta4</li><li>jboss-jaxr, v1.2.0.GA</li><li>jboss-ejb3-cache, v0.11.1</li><li>jboss-ejb3-ext-api, v0.1.2.Beta1</li><li>jboss-ejb3-impl, v0.1.2.Beta1</li><li>jboss-jaspi-api, v1.0-BETA1</li><li>jboss-javaee, v5.0.0.Beta3Update1</li><li>jboss-security-spi, v2.0.2.Beta1</li><li>jbosssx, v2.0.2.beta1</li><li>jbosssx-client, v2.0.2.beta</li><li>jbossts, v4.3.0.BETA2</li><li>jboss-vfs, v2.0.0.Beta6</li><li>jbossws-native50, 2.0.2.GA</li><li>jbossxb, v2.0.0.CR5</li><li>jms-integration-tests, v1.0.1.GA</li><li>messaging, v1.4.0.SP1</li><li>metadata, v1.0.0.Beta4</li><li>microcontainer, v2.0.0.Beta8</li><li>profiler/jvmti, v1.0.0.CR5</li><li>remoting, v2.2.2.SP3</li><li>serialization, v1.0.3.GA</li><li>test, v1.0.4.GA</li><li>jboss-web, v2.1.0.CR11</li><li>jgroups, v2.6.1.GA</li></ul>Thirdparty
Library Updates<br><ul><li>antlr, v2.7.6</li><li>apache-avalon,v 4.1.5</li><li>apache-avalon-logkit, v1.2</li><li>apache-bcel, v5.1</li><li>apache-beanutils, v1.7.0</li><li>apache-bsf, v2.3.0</li><li>apache-codec, v1.3.0</li><li>apache-collections, v3.1</li><li>apache-digester, v1.7</li><li>apache-discovery, v0.4</li><li>apache-fileupload, v1.1.1</li><li>apache-httpclient, v3.0.1</li><li>apache-jaxme, v0.2-cvs</li><li>apache-log4j, v1.2.14</li><li>apache-logging, v1.1.0.jboss</li><li>apache-myfaces, v1.1.3</li><li>apache-scout, v0.7rc2</li><li>apache-slide, v2.1</li><li>apache-velocity, v1.4jboss</li><li>apache-xalan, v2.7.0.patch01</li><li>apache-xerces, v2.9.0</li><li>apache-xmlsec, v1.3.0</li><li>beanshell, v1.3.0</li><li>cglib, v2.1.3</li><li>commons-el, v1.0</li><li>dom4j, v1.6.1</li><li>easymock, v1.1</li><li>gjt-jpl-util, v1.0</li><li>gnu-getopt, v1.0.12</li><li>hsqldb, v1.8.0.8</li><li>jacorb, v2.3.0jboss.patch5</li><li>jaxen, v1.1</li><li>jfreechart, v0.9.20</li><l!
i>joesnmp, v0.3.4</li><li>juddi, v0.9RC4</li><li>junit, v3.8.2</li><li>nekohtml, v0.9.1</li><li>objectweb-joramtests, v1.5</li><li>odmg, v3.0</li><li>opensaml, v1.1b</li><li>oswego-concurrent, v1.3.4-jboss-update1</li><li>qdox, v1.6.1</li><li>quartz, v1.5.2</li><li>sleepycat, v3.0.12</li><li>spring, v2.0</li><li>sun-jaf, v1.1</li><li>sun-javacc, v3.2</li><li>sun-javamail, v1.4</li><li>sun-jsf, v1.2_04_P02</li><li>sun-jstl, v1.2</li><li>sun-opends, v0.1.0.build016</li><li>sun-servlet, v2.5</li><li>sun-xacml, v2.0</li><li>trove, v1.0.2</li><li>woodstox, v3.1.1</li><li>xdoclet, v1.2.3</li><li>xmlunit-xmlunit, v1.0</li></ul><ul></ul><h1><a name="Details">Detailed Release
Notes</a></h1>
<h3>Includes versions: JBossAS-5.0.0.Beta3</h3>
More information about the jboss-cvs-commits
mailing list