[jboss-cvs] JBossAS SVN: r78600 - 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:27:56 EDT 2008
Author: dimitris at jboss.org
Date: 2008-09-16 16:27:56 -0400 (Tue, 16 Sep 2008)
New Revision: 78600
Modified:
tags/JBoss_5_0_0_CR2/build/docs/readme.html
Log:
3rd pass.
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:02:58 UTC (rev 78599)
+++ tags/JBoss_5_0_0_CR2/build/docs/readme.html 2008-09-16 20:27:56 UTC (rev 78600)
@@ -13,14 +13,11 @@
Java EE 5 conformance testing
certification requirements! Obviously, this is a big 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>Thanks to the JBoss Community with have incorporated a large number of bug fixes and improvement.</p><p>, component updates and </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
+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
+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
@@ -31,8 +28,7 @@
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>. Please note how the -sources.jar are also downloaded, starting from CR2.</p><p>A secondary target for this release was to improve support for Java 6. JBossAS
-4.2.3.GA 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
+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
@@ -45,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>
@@ -119,8 +106,7 @@
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-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 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>JBossAS 5.0.0.CR2 can be compiled with both Java5 & Java6. The Java5 compiled
@@ -139,9 +125,9 @@
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>Various *-beans.xml
-configuration files have been renamed to *-jboss-beans.xml to
-avoid conflicts with spring configuration files.</li><li>JBoss
+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
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
@@ -169,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></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 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>
<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
@@ -209,9 +195,7 @@
<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>Use of the jboss.jgroups.udp.mcast_port property to control easy configuration of multicast port, JBS-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
+</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
@@ -222,7 +206,7 @@
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
@@ -232,7 +216,9 @@
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
+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,
@@ -240,7 +226,7 @@
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><li>Bootstrap
-time has improved, compared to AS5 CR1, but it still somewhat
+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><li>JBoss should now be able to start when JBOSS_HOME contains spaces, JBAS-5796.</li>
More information about the jboss-cvs-commits
mailing list