[jboss-cvs] JBossAS SVN: r75549 - trunk/build/docs.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Wed Jul 9 09:46:28 EDT 2008
Author: dimitris at jboss.org
Date: 2008-07-09 09:46:28 -0400 (Wed, 09 Jul 2008)
New Revision: 75549
Modified:
trunk/build/docs/readme.html
Log:
JBAS-5748, Update links in ROOT.war/index.html
Modified: trunk/build/docs/readme.html
===================================================================
--- trunk/build/docs/readme.html 2008-07-09 13:45:30 UTC (rev 75548)
+++ trunk/build/docs/readme.html 2008-07-09 13:46:28 UTC (rev 75549)
@@ -5,7 +5,8 @@
<body><a href="http://www.jboss.com/index"><img src="http://www.jboss.com/themes/jbosstheme/img/logo.gif" alt="JBoss - A Division of Red Hat" border="0"></a><h1>JBoss
5.0.0.CR1
Release Notes</h1>
-<p>This is the first <a href="http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossProductVersioning"><span style="text-decoration: none; font-weight: 700;">Candidate Release</span></a>
+<p>This is the first <a href="http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossProductVersioning"><span style="text-decoration: none; font-weight: 700;">Candidate
+Release</span></a>
release of the <b>JBoss 5.0.x</b> series for the <b>Java
EE™</b>
5 codebase! This release almost completes the Java EE5 conformance
@@ -19,13 +20,17 @@
available the various EE services as independent projects, so that they
can be wired-together and be consumed ala-cart inside
different runtime environments and not just inside the JBoss
-Application Server.</p><p>If you are building JBossAS from source
-you'll notice we are migrating to a maven2 build. At this point
+Application Server.</p><p>If you are building JBossAS from
+source
+you'll notice we are migrating to a maven2 build. At this
+point
the build is a hybrid one because it declares all JBoss
dependencies as maven2 artifacts, however after the dependencies are
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 information
+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
+information
on the APIs that
make up Java EE 5, see
<a href="http://java.sun.com/javaee/reference/index.jsp">Java
@@ -89,7 +94,8 @@
Enterprise Middleware Stack (JEMS), included with JBoss 5 as the
default messaging provider. It is also the backbone of the <a href="http://www.jboss.com/products/esb">JBoss ESB</a>
infrastructure. JBoss Messaging is a complete rewrite of JBossMQ, which
-is the default JMS provider for the JBoss AS 4.x series.</li> <li><a href="http://www.jboss.com/products/jbosscache">JBossCache</a> that comes in two flavors. A traditional tree-structured node-based
+is the default JMS provider for the JBoss AS 4.x series.</li> <li><a href="http://www.jboss.com/products/jbosscache">JBossCache</a> that
+comes in two flavors. A traditional tree-structured node-based
cache and a <a href="http://labs.jboss.com/file-access/default/members/jbosscache/freezone/docs/2.0.0/PojoCache/en/html/index.html">
PojoCache</a>, an in-memory, transactional, and replicated cache
system that allows users to operate on simple POJOs transparently
@@ -105,18 +111,43 @@
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-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,
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 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
+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
+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
+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
(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>.
@@ -137,7 +168,9 @@
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 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>- 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
@@ -171,7 +204,17 @@
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>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
+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>
@@ -179,14 +222,22 @@
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
+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 Farm service is removed. Distributed
+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
+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>
+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
@@ -194,7 +245,20 @@
This will be eventually reduced to a single pass.</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.CR1 check the <a style="font-family: monospace;" href="http://anonsvn.jboss.org/repos/jbossas/tags/JBoss_5_0_0_CR1/component-matrix/pom.xml">pom.xml</a> found in the component-matrix directory of the source code distribution. To see the maven dependency tree you can also do a '<span style="font-family: monospace;">mvn dependency:tree</span>' from the <span style="font-family: monospace;">thirdparty</span> directory of the source code distro.<br><br>Some rather important used jboss project versions are listed below:<br><ul><li>JBoss Transactions, v4.3.0.GA</li><li>JBoss WebServices, v3.0.2.GA</li><li>JBoss Messaging, v1.4.1.CR1</li><li>JBoss Web, v2.1.1.CR3</li><li>JBoss AOP, 2.0.0.CR13</li><li>JBoss EJB3, v0.1.6</li><li>JBoss Microcontainer, v2.0.0.Beta16</li><li>JBoss Security, v2.0.2.CR5</li><li>Hibernate, v3.3.0.CR1</li><li>Hibernate Entity Manager, v3.4.0.CR1</li><li>Hibernate Annotations, v3.4.0.CR1</li><li>JBoss Cache POJO, v2.1.0.GA</li><li>J!
Boss Cache Core, v2.1.1.GA</li><li>JGroups, v.2.6.3.CR1</li></ul>
+with JBoss AS 5.0.0.CR1 check the <a style="font-family: monospace;" href="http://anonsvn.jboss.org/repos/jbossas/tags/JBoss_5_0_0_CR1/component-matrix/pom.xml">pom.xml</a>
+found in the component-matrix directory of the source code
+distribution. To see the maven dependency tree you can also do a '<span style="font-family: monospace;">mvn dependency:tree</span>'
+from the <span style="font-family: monospace;">thirdparty</span>
+directory of the source code distro.<br><br>Some rather
+important used jboss project versions are listed below:<br><ul><li>JBoss
+Transactions, v4.3.0.GA</li><li>JBoss WebServices, v3.0.2.GA</li><li>JBoss
+Messaging, v1.4.1.CR1</li><li>JBoss Web, v2.1.1.CR3</li><li>JBoss
+AOP, 2.0.0.CR13</li><li>JBoss EJB3, v0.1.6</li><li>JBoss
+Microcontainer, v2.0.0.Beta16</li><li>JBoss Security,
+v2.0.2.CR5</li><li>Hibernate, v3.3.0.CR1</li><li>Hibernate
+Entity Manager, v3.4.0.CR1</li><li>Hibernate Annotations,
+v3.4.0.CR1</li><li>JBoss Cache POJO, v2.1.0.GA</li><li>JBoss
+Cache Core, v2.1.1.GA</li><li>JGroups, v.2.6.3.CR1</li></ul>
<h1><a name="Details">Detailed
Release
Notes</a></h1>
@@ -679,8 +743,8 @@
be obtained from the following locations.
<ul><li><a href="http://www.jboss.org/jbossas/docs">JBoss
AS Documentation</a></li>
-<li><a href="http://wiki.jboss.org/">JBoss Wiki</a></li>
-<li><a href="http://jira.jboss.com/jira/browse/JBAS">JBoss
+<li><a href="http://wiki.jboss.org">JBoss Wiki</a></li>
+<li><a href="http://jira.jboss.org/jira/browse/JBAS">JBoss
JIRA</a></li>
<li><a href="http://www.jboss.org/index.html?module=bb">JBoss
Forums</a></li>
More information about the jboss-cvs-commits
mailing list