[jboss-cvs] JBossAS SVN: r75203 - trunk/build/docs.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Mon Jun 30 05:38:37 EDT 2008
Author: dimitris at jboss.org
Date: 2008-06-30 05:38:36 -0400 (Mon, 30 Jun 2008)
New Revision: 75203
Modified:
trunk/build/docs/readme.html
Log:
JBAS-5688, second pass of releases notes.
Modified: trunk/build/docs/readme.html
===================================================================
--- trunk/build/docs/readme.html 2008-06-30 08:18:44 UTC (rev 75202)
+++ trunk/build/docs/readme.html 2008-06-30 09:38:36 UTC (rev 75203)
@@ -10,7 +10,7 @@
EE™</b>
5 codebase! This release almost completes the Java EE5 conformance
testing certification requirements, however note that only the
-final GA version will be declared as EE5 conformant.</p><p>Some
+final GA version will be declared as conformant.</p><p>Some
important changes relative to the last Beta4 release has been the
further breaking out of internal subsystems into independent projects
most prominent of which is the breaking out of the EJB3 project and its
@@ -113,22 +113,18 @@
(JBAS-5031). The distribution is compiled with Java 5 and should be
able to run without problems using a Java 6 runtime. If you still have
problems starting JBoss with 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></li></ul><br><ul><li>If
+as described in <a href="http://jira.jboss.com/jira/browse/JBAS-4491">JBAS-4491</a>.</li><li>JaasSecurityDomain has been converted to a simple bean (from an MBean), see JBAS-5356.</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 <a href="http://anonsvn.jboss.org/repos/jbossas/projects/vfs/trunk/src/main/java/org/jboss/virtual/VFSUtils.java">VFSUtils.java</a> class. </li><li>Hibernate-core is now using<span style="font-family: monospace;"> slf4j-api</span> as a logging facade. To properly integrate that in JBossAS we have created an slf4j-to-jboss-logging adapter (<span style="font-family: monospace;">slf4j-jboss-logging.jar</span>) that
+creates a static binding between sl4j and jboss-logging-spi . The
+jboss-logging default implementation is configured to use log4j. See
+JBAS-5519.</li><li>The <span style="font-family: monospace;">client/jbossall-client.jar</span> library that used to bundle the majority of jboss client libraries, is now referencing them instead through the <span style="font-family: monospace;">Class-Path</span> manifest entry. This allows swapping included libraries (e.g.<span style="font-family: monospace;"> jboss-javaee.jar</span>) without having to re-package <span style="font-family: monospace;">jbossall-client.jar</span>. On the other hand, it requires that you have <span style="font-family: monospace;">jbossall-client.jar</span> together with the other client/*.jar libraries, so they can be found. See JBAS-4355.</li><li>If
using proprietary JBoss/EJB3 annotations, those have moved
-into the <span style="font-family: monospace;">org.jboss.ejb3.annotation
+(since Beta4) 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
+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
@@ -136,12 +132,12 @@
resembles that of the 4.x
series with some notable differences:</p>
<ul> <li>bin - start scripts and run.jar</li> <li>client
-- client jars</li> <li>docs - docs, chemas/dtds, examples</li>
+- client jars</li> <li>docs - docs, schemas/dtds, examples</li>
<li>lib - core bootstrap jars, somewhat different with the <b>introduction
of the microcontainer</b> and breakup of jboss-common.</li>
<li>server - the same server configuration dirs.<ul> <li>default
configuration<ul> <li>conf</li> <ul> <li><b>bootstrap-beans.xml
-</b>- new mc kernel bootstrap configuration</li> <li><b>jax-ws-catalog.xml
+</b>- new mc kernel bootstrap configuration referencing other<br>configuration files that contain the beans that setup each individual subsystem.</li><ul><li>classloader.xml</li><li>aop.xml</li><li>jmx.xml</li><li>deployers.xml</li><li>profile-service.xml</li></ul> <li><b>jax-ws-catalog.xml
</b>- oasis catalog driven schema/dtd namespace configuration</li>
<li><b>jbossjta-properties.xml </b>- new JBossTS
properties</li> <li>jboss-service.xml - legacy static
@@ -163,7 +159,7 @@
<li>jbossws.deployer - web services deployers</li>
<li>ear-deployer-beans.xml - ear deployers</li>
<li>ejb-deployer-beans.xml - ejb2.x deployers</li>
-<li>metadata-beans.xml - metadata handlers</li>
+<li>metadata-deployer-beans.xml - metadata handlers</li>
<li>security-deployer-beans.xml - security deployers</li>
<li>profileservice-beans.xml.bak - an example of the repository
based profile service</li>
@@ -175,9 +171,7 @@
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/browse/JBAS-4967">JBAS-4967</a>).
-</li></ul>EJB3
+for useJK is whether jvmRoute is set (<a class="external" href="http://jira.jboss.com/jira/browse/JBAS-4961">JBAS-4961</a>).</li><li>Total replication (rather than buddy replication) is the default setting for session replication (JBAS-5085).</li><li>The transaction manager configuration has moved from <span style="font-family: monospace;">conf/jboss-service.xml</span> to <span style="font-family: monospace;">deploy/transaction-service.xml</span> (JBAS-5103).</li><li>The default <span style="font-family: monospace;">conf/jboss-log4j.xml</span> configuration now includes the thread name, for entries in<span style="font-family: monospace;"> log/server.log</span> (JBAS-5274).</li><li>All the security related configuration files are now grouped under the <span style="font-family: monospace;">deploy/security</span> directory (JBAS-5318).</li><li>Loopback is now set to true for all JGroups UDP stacks (JBAS-5323).</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.Beta4">wiki</a>
@@ -192,9 +186,9 @@
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>
+maintained.</li><li>The <span style="font-family: monospace;">HASingletonDeploymentScanner</span> that monitors and deploys content from <span style="font-family: monospace;">deploy-hasingleton</span> directory is working again, JBAS-5686. </li>
<li>The JSR77 view of the server is not implemented yet.</li><li>There
-is a noticable delay (10-15secs) in the start-up time of the
+is a noticeable delay (10-15secs) in the start-up time of the
application server, when compared to the 4.2.x series. This is due to
multiple passes of annotation processing from different subsystems.
This will be eventually reduced to a single pass.</li>
More information about the jboss-cvs-commits
mailing list