[jboss-cvs] JBossAS SVN: r78602 - trunk/build/docs.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Tue Sep 16 16:49:17 EDT 2008
Author: dimitris at jboss.org
Date: 2008-09-16 16:49:16 -0400 (Tue, 16 Sep 2008)
New Revision: 78602
Modified:
trunk/build/docs/readme.html
Log:
JBAS-5962, done.
Modified: trunk/build/docs/readme.html
===================================================================
--- trunk/build/docs/readme.html 2008-09-16 20:47:38 UTC (rev 78601)
+++ trunk/build/docs/readme.html 2008-09-16 20:49:16 UTC (rev 78602)
@@ -9,15 +9,15 @@
Release</span></a>
release of the <b>JBoss 5.0.x</b> series for the <b>Java
EE™</b>
-5 codebase, that completes the Java EE 5 conformance testing
-certification requirements!</p><p></p><p></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
-many dependencies. Those changes should not affect directly the end
-user but they are an important part of the JBoss strategy of making
+5 codebase and the first JBossAS release that fully complies with the
+Java EE 5 conformance testing
+certification requirements! This is an important milestone in the
+development of JBossAS as we will have more time now to spend on
+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
-can be wired-together and be consumed ala-cart inside
+can be wired-together and be consumed a-la-carte inside
different runtime environments and not just inside the JBoss
Application Server.</p><p>If you are building JBossAS from
source
@@ -28,7 +28,12 @@
resolved/imported the legacy ant based build is used to compile and
build the distribution. This will change to a full maven build
at
-some point in time. The jboss maven repo can be found <a href="http://repository.jboss.org/maven2/org/jboss/">here</a>.</p>For
+some point in time. The jboss maven repo can be found <a href="http://repository.jboss.org/maven2/org/jboss/">here</a>. Starting from AS5 CR2, please note how the -sources.jar are also downloaded.</p><p>Another target for this release was to improve support for Java 6. JBossAS 5 CR2 can be build with both JDK5 <span style="font-style: italic;">and</span><span style="font-weight: bold; font-style: italic;"> </span>JDK6. The JDK5 compiled
+binaries have undergone more rigorous testing, they constitute our certified
+version and can run under both Java 5 & 6 VMs (with a few configuration
+changes for JDK6, see the configuration section below). The JDK6 compiled
+binaries include support for the JDBC 4 APIs, but this should be considered
+experimental at this point.</p>For
information
on the APIs that
make up Java EE 5, see
@@ -36,19 +41,10 @@
EE APIs & Docs</a>. A tutorial on Java EE 5 can be found
<a href="http://java.sun.com/javaee/5/docs/tutorial/doc/">here</a>.
<p>A sample Java EE 5 application that can be
-run on top of JBoss 5.0.0.CR1 and demonstrates many interesting
+run on top of JBoss 5 and demonstrates many interesting
technologies is the <b><i>Seam Booking Application</i></b>
-available <a href="http://repository.jboss.org/maven2/org/jboss/seam/examples/">here</a>. This
-application makes use of the following technologies running on
-JBoss 5:</p>
-<ul><li>EJB3</li>
-<ul> <li>Stateful Session Beans</li> <li>Stateless
-Session Beans</li> <li>JPA (w/ Hibernate validation)</li>
-</ul><li>JSF</li>
-<ul> <li>Facelets</li> <li>Ajax4JSF</li>
-</ul><li><a href="http://www.jboss.com/products/seam">Seam</a></li>
-</ul>The <a href="http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossSeam">JBoss
-Seam Wiki</a> links to many interesting topics about Seam.<h2>Overview</h2>
+available <a href="http://repository.jboss.org/maven2/org/jboss/seam/examples/">here</a>. Check out the <a href="http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossSeam">JBoss
+Seam Wiki</a> that links to many interesting topics about Seam.</p><h2>Overview</h2>
<ul> <li><a href="#Highlights">Highlights</a></li>
<li><a href="#Compatibility">Compatibility Issues</a></li>
<li><a href="#Configuration">Configuration Issues</a></li>
@@ -101,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
@@ -110,24 +106,28 @@
Tomcat that includes the Apache Portable Runtime (APR) and Tomcat
native technologies to achieve scalability and performance
characteristics that match and exceed the Apache Http server.</li>
-</ul><p>Minor feature additions for this release include:</p><ul><li>JBAS-4383,
-a facility for changing the default JSF implementation.</li><li>JBAS-5119,
-the default classloader used in JBoss in now the VFS Classloader.</li><li>JBAS-5163,
-listThreadDump() now shows deadlocks under a Java 6 runtime.</li><li>JBAS-5281,
-a new flag to control scanning classes for ejb annotations in the war
-classpath</li><li>JBAS-5329, jgroups channels sharing
-transports.</li></ul><p>JBoss 5 includes numerous
-features and bug fixes,
+</ul><p>Minor feature additions for this release include:</p><ul><li>JBAS-5862, a new look for the jmx-console</li><li>JBAS-5793, array interception for POJOs stored in web sessions with FIELD granularity.</li><li>JBAS-5192, a POJO based replacement for the JBoss 4 ServiceBindingManager (WIP).</li><li>JBAS-5822, support of the new ServiceBindingManager in old -service.xml deployments.</li></ul><p>JBoss 5 includes 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 is compiled and tested under both under Java 5 and Java 6
-(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>JaasSecurityDomain
-has been converted to a simple bean (from an MBean), see JBAS-5356.</li><li>JBoss
+<h2><a name="Compatibility">Compatibility Issues</a></h2>JBossAS 5.0.0.CR2 can be compiled with both Java5 & Java6. The Java5 compiled
+binary is our primary/recommended binary distribution. It has undergone rigorous
+testing and can run under both a Java 5 and a Java 6 runtime. When running under
+Java 6 you need to manually copy the following libraries from the
+JBOSS_HOME/client directory to the JBOSS_HOME/lib/endorsed directory, so that
+the JAX-WS 2.0 apis supported by JBossWS are used:
+<ul><li>jbossws-native-saaj.jar</li><li>jbossws-native-jaxrpc.jar</li><li>jbossws-native-jaxws.jar</li><li>jbossws-native-jaxws-ext.jar</li></ul>The
+other option is to download the jdk6 distribution
+(jboss-5.0.0.CR2-jdk6.zip) in which case no configuration changes are
+required. If you still have problems using 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>. Other
+potential problems under a Java 6 runtime include:<br><ul><li>ORB getting prematurely destroyed when using Sun JDK 6 (see Sun Bug ID: <a href="http://bugs.sun.com/bugdatabase/view_bug.do;jsessionid=fd40a0e2c4c9b79adab12ca088bd?bug_id=6520484">6520484)</a></li><li>Unimplemented methods in Hibernate for JDK6 interfaces.</li><li>When JBossAS 5 is compiled with Java 6, support for the extended JDBC 4
+API is included in the binary, however this can only be used under a Java 6
+runtime. In this case no manual configuration steps are necessary. It should be
+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>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
@@ -150,13 +150,12 @@
using proprietary JBoss/EJB3 annotations, those have moved
(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
+Those are now included in a new artifact, jboss-ejb3-ext-api.jar</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>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>
+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
@@ -166,9 +165,9 @@
<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
+configuration<ul> <li>conf</li> <ul> <li><b>bootstrap.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.xml</li></ul>
+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>bindings.xml (*New POJO-based ServiceBindingManager*)</li><li>profile.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
@@ -188,17 +187,15 @@
<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 - ejb2.x deployers</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
+<li>jbossws.deployer - web services deployers</li><li>seam.deployer - SEAM deployer</li><li>alias-deployers-jboss-beans.xml</li><li>clustering-deployers-jboss-beans.xml</li>
+<li>ear-deployer-jboss-beans.xml - ear deployers</li>
+<li>ejb-deployer-jboss-beans.xml - ejb2.x deployers</li>
+<li>metadata-deployer-jboss-beans.xml - metadata handlers</li>
+<li>security-deployer-jboss-beans.xml - security deployers</li>
+<li>profileservice-jboss-beans.xml.bak - an example of the repository
based profile service</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
+</ul></li></ul></li></ul>Various configuration issues:<ul><li>Use of the jboss.jgroups.udp.mcast_port property to control easy configuration of multicast port, JBAS-2395</li><li>Overriding of ra.xml properties in jboss-ra.xml, JBAS-3343</li><li>Support for defining depenndencies in JCA adapters, JBAS-4508</li><li>Controlling command line arguments for the appClientLauncher, JBAS-5888.</li><li>Shutdown.sh now accepts a JNDI url, JBAS-5922.</li><li>DeleteWorkDirOnContextDestroy property for JSP pages, JBAS-5453.</li><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
@@ -209,39 +206,30 @@
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>
+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
+deployers/ejb3.deployer/META-INF/ejb3-deployers-jboss-beans.xml. For more
details check out this <a href="http://wiki.jboss.org/wiki/Wiki.jsp?page=ToAS5.0.0.Beta4">wiki</a>
page.<br><br>For security related configuration changes,
please consult this <a href="http://wiki.jboss.org/wiki/Wiki.jsp?page=SecurityInJBoss5">wiki</a>
-page.<br><h2><a name="Other">Other
-Issues</a></h2><ul><li>Problems
-with deploying Seam applications against AS5.0.0.Beta4 have
-been
-resolved. Now the Seam examples are deployed as part of the standard
-JBoss AS testsuite, JBAS-5190.</li><li>The Hibernate
-deployer (.har) is again operational, JBAS-5232.</li><li>Hot
-undeployment on Windows (i.e. removing files from the ./deploy
-directory) have been been fixed, JBAS-4310.</li><li>Issues
-with hot deployment of .jars have also been fixed, JBAS-4220.</li><li>The
+page.<br>For clustering
+related changes, check out the <a href="http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossAS5ClusteringChanges">Wiki</a>
+for more info.<br><h2><a name="Other">Other
+Issues</a></h2><ul><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 <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 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
+maintained.</li><li>The JSR77 view of the server is not implemented yet.</li><li>Bootstrap
+time has improved compared to AS5 CR1, but it still somewhat
+slower 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>
+This will be eventually reduced to a single pass.</li><li>JBoss should now be able to start when JBOSS_HOME contains spaces, JBAS-5796.</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.CR2 check the <a style="font-family: monospace;" href="http://anonsvn.jboss.org/repos/jbossas/tags/JBoss_5_0_0_CR2/component-matrix/pom.xml">pom.xml</a>
More information about the jboss-cvs-commits
mailing list