[jboss-cvs] JBossAS SVN: r82050 - branches/Branch_5_0/build/docs.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Thu Dec 4 11:30:21 EST 2008
Author: dimitris at jboss.org
Date: 2008-12-04 11:30:21 -0500 (Thu, 04 Dec 2008)
New Revision: 82050
Modified:
branches/Branch_5_0/build/docs/readme.html
Log:
take two
Modified: branches/Branch_5_0/build/docs/readme.html
===================================================================
--- branches/Branch_5_0/build/docs/readme.html 2008-12-04 16:07:27 UTC (rev 82049)
+++ branches/Branch_5_0/build/docs/readme.html 2008-12-04 16:30:21 UTC (rev 82050)
@@ -165,19 +165,7 @@
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>JBossAS 5 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>
-
<h2><a name="Compatibility">Compatibility Issues</a></h2>
-
JBossAS 5.0.0.GA 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
@@ -219,10 +207,13 @@
<ul>
-<li>All
+<li>JBossMQ has been removed from the distribution and is no longer
+supported in AS5. JBoss Messaging Service is now the default JMS
+provider.</li><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
@@ -232,7 +223,14 @@
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>
+class.</li><li>VFS
+uses an internal caching mechanism to speed up access to deployment
+artifacts. This means that files in deploy/ remain open as long as they
+are accessed and then closed by a reaper thread after a 5 seconds
+innactivety. On window platforms this may cause locking issues if files
+are re-deployed too quickly. In this case you may want to turn-off the
+reaper by specifiying the <span style="font-family: monospace;">-Djboss.vfs.forceNoReaper=true</span> property in the command line.</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
@@ -260,38 +258,79 @@
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
+Cache 3.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>
<li>The ClassPathExtension MBean
has been replaced with a VFS classloader definition, see
-JBAS-5446.</li>
+JBAS-5446.</li><li>The old JMX-based ServiceBindingManager has been replaced by a POJO-based ServiceBindingManager, see <a href="https://jira.jboss.org/jira/browse/JBAS-5192">JBAS-5192</a>.</li>
+ <li>The
+Farm service from 4.x has been removed.</li>
+ <li>JBoss 5 is stricter when it comes to verifying/deploying
+JavaEE artifacts. EJB3 deployments that run in AS 4.2 may fail in AS5.
+We have tried to keep the validation messages as accurate as possible
+in order to help you modify your deployment
+descriptors/annotations to be in-line with the JavaEE 5 requirements.</li>
+
</ul>
+<h2><a name="Configuration">Configuration Issues</a></h2>
-For strict JavaEE compatibility compliance you can:<br>
+<p>JBossAS 5.0.0.GA introduces two new configuration, the <span style="font-family: monospace; font-weight: bold;">standard</span><span style="font-weight: bold;"> </span>and the <span style="font-family: monospace; font-weight: bold;">web</span> config.<br>
+</p>
<ul>
-
-<li>Enable call-by-value in
-deployers/ear-deployer-jboss-beans.xml<br>
+<li>The <span style="font-weight: bold;">standard</span> config is
+the configuration that has been tested for JavaEE compliance. The major
+differences with the existing configurations is that call-by-value and
+deployment isolation are enabled by default, along with support for
+rmiiiop and juddi (taken from the <span style="font-weight: bold;">all</span> config).</li><ul><li style="font-family: monospace;">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>
+name="callByValue">true</property><br>
+<property name="isolated">true</property></li><li style="font-family: monospace;">conf/jboss-service.xml call-by-value for
+"jboss:service=Naming"<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>
+name="CallByValue">true</attribute></li><li><span style="font-family: monospace;">conf/jndi.properties</span><span style="font-family: monospace;"><br>
+java.naming.factory.initial=org.jboss.iiop.naming.ORBInitialContextFactory</span></li><li style="font-family: monospace;">conf/jacorb.properties<br>
+deploy/iiop-service.xml<br>
+lib/avalon-framework.jar<br>
+lib/jacorb.jar</li><li><span style="font-family: monospace;"><span style="font-family: monospace;">deploy/juddi-service.sar</span></span></li></ul><li>The <span style="font-weight: bold;">web</span> config is a new <span style="font-style: italic; font-weight: bold;">experimental</span>lightweight
+configuration created around JBoss Web that will follow
+the developments of the JavaEE 6 web profile. Except for the
+servlet/jsp container it provides support for JTA/JCA and JPA. It also
+limits itself to allowing access to the server only through the http
+port. Please
+note that this configuration is not JavaEE certified and will most
+likely change in the following
+releases.<br>
+ </li>
</ul>
-<h2><a name="Configuration">Configuration Issues</a></h2>
+Another notable change is that the majority of the libraries common to
+the different configurations have moved to a new shared location, J<span style="font-family: monospace; font-weight: bold;">BOSS_HOME/common/lib/</span>.
+This is so we avoid having multiple copies of the same libraries in the
+distribution. The location of the common library directory can be
+controlled by the following properties:<br>
-<p>This section lists changes that
-could affect the server
-configuration.</p>
+<ul>
+<li style="font-family: monospace;">jboss.common.base.url defaulting to ${jboss.home.url}/common
+ </li><li><span style="font-family: monospace;">jboss.common.lib.url defaulting to ${jboss.common.base.url}/lib</span>
+ </li>
+</ul>
+The common library directory is shared by all the configurations except for the <span style="font-weight: bold;">minimal</span> config. It is referenced in the very beginning of every configuration's <span style="font-family: monospace;">conf/jboss-service.xml</span>.<br>
+
+<br>
+
+<div style="margin-left: 40px;"><span style="font-family: monospace;"><classpath codebase="${jboss.server.lib.url}" archives="*"/></span><br style="font-family: monospace;">
+<span style="font-family: monospace;"><classpath codebase="${jboss.common.lib.url}" archives="*"/><br>
+</span></div>
+
+<br>
+
+You can see that the library directory of the individual configurations
+is still in place, although in some cases it's empty (e.g.
+JBOSS_HOME/server/default/lib/)
<p>The directory structure of
JBoss 5
resembles that of the 4.x
@@ -302,7 +341,11 @@
<li>bin - start scripts and
run.jar</li>
<li>client
-- client jars</li>
+- client jars - note how <span style="font-weight: bold;">jbossall-client.jar</span> is now referencing the other client jars.</li><li style="font-weight: bold;">common</li>
+ <ul>
+ <li><span style="font-weight: bold;">lib</span></li>
+ </ul>
+
<li>docs - docs, schemas/dtds,
examples</li>
<li>lib - core bootstrap jars,
@@ -312,24 +355,35 @@
<li>server - the same server
configuration dirs.
<ul>
-<li>default
-configuration
+<li><span style="font-style: italic;">xyz</span> configuration
<ul>
<li>conf</li>
<ul>
<li><b>bootstrap.xml
</b>- new mc kernel
-bootstrap configuration referencing other<br>
-configuration
+bootstrap configuration referencing other </li><li>configuration
files that contain the beans that setup each individual subsystem.</li>
+ <ul>
+ <li><span style="font-weight: bold;">bootstrap</span></li>
+ </ul>
+
<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><span style="font-weight: bold;">vfs.xml</span> - vfs initialization</li>
+ <li style="font-weight: bold;">classloader.xml</li>
+ <li style="font-weight: bold;">aop.xml</li>
+ <li><span style="font-weight: bold;">jmx.xml</span> - legacy JMX support</li>
+ <li style="font-weight: bold;">deployers.xml</li>
+ <li><span style="font-weight: bold;">bindings.xml</span>
+(POJO-based ServiceBindingManager & port bindings)</li>
+ <li><span style="font-weight: bold;">profile-repository.xml</span> (profile service enabled deployment repository)</li>
+ </ul>
+
+
+
+
+
+
</ul>
<li><b>jax-ws-catalog.xml
</b>- oasis catalog
@@ -339,7 +393,7 @@
properties</li>
<li>jboss-service.xml
- legacy static
-mbeans for compatibility</li>
+mbeans for compatibility, somewhat reduced</li>
<li>jndi.properties -
the
same jndi props</li>
@@ -362,6 +416,18 @@
</ul>
<li>deploy/ - the same
deploy directory.</li>
+ <ul>
+ <li>...</li>
+ <li><span style="font-weight: bold;">jca-jboss-beans.xml</span></li>
+ <li><span style="font-weight: bold;">hdscanner-jboss-beans.xml</span> - the hot deployment scanner</li>
+ <li><span style="font-weight: bold;">legacy-invokers-service.xml</span></li>
+ <li><span style="font-weight: bold;">profileservice-jboss-beans.xml</span></li>
+ <li><span style="font-weight: bold;">remoting-jboss-beans.xml</span></li>
+ <li><span style="font-weight: bold;">transaction-jboss-beans.xml</span></li>
+ <li><span style="font-weight: bold;">vfs-jboss-beans.xml<br>
+ </span></li>
+ </ul>
+
<li><b>deployers/
- <a href="http://wiki.jboss.org/wiki/Wiki.jsp?page=JBoss5DeploymentFramework">new
vdf deployers</a></b>
@@ -381,11 +447,15 @@
<li>seam.deployer -
SEAM deployer</li>
<li>alias-deployers-jboss-beans.xml</li>
-<li>clustering-deployers-jboss-beans.xml</li>
+<li>clustering-deployers-jboss-beans.xml</li><li>dependency-deployers-jboss-beans.xml</li>
+ <li>directory-deployer-jboss-beans.xml</li>
+
<li>ear-deployer-jboss-beans.xml
- ear deployers</li>
<li>ejb-deployer-jboss-beans.xml
-- ejb2.x deployers</li>
+- ejb2.x deployers</li><li>hibernate-deployer-jboss-beans.xml</li>
+ <li>jsr77-deployers-jboss-beans.xml</li>
+
<li>metadata-deployer-jboss-beans.xml
- metadata handlers</li>
<li>security-deployer-jboss-beans.xml
@@ -396,7 +466,7 @@
</ul>
</li>
<li>lib/ - the same
-static library jars</li>
+static library jars with a few jars, as most have moved to top level common/lib</li>
</ul>
</li>
</ul>
@@ -406,9 +476,10 @@
Various configuration issues:
<ul>
-<li>Use of the
+<li>A new <span style="font-family: monospace;">jboss.server.log.threshold </span>system property can be used to control the log/server.log threshold. It defaults to DEBUG.</li><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
@@ -468,22 +539,13 @@
<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 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>
-<li>JBoss should now be able to
-start when JBOSS_HOME contains spaces, JBAS-5796.</li>
+slower when compared to the 4.2.x series, due to the extensive
+annotation scanning that goes on behind the scenes. There are ways to
+optimize the annotation scanning, especially for large deployments.
+Check the <a href="https://www.jboss.org/community/docs/DOC-13178">JBoss Wiki </a>for more information.</li>
+
</ul>
<h2><a name="Libraries">Library Updates</a></h2>
@@ -497,9 +559,10 @@
directory of the source code distro.<br>
<br>
-
Some rather
-important used jboss project versions are listed below:<br>
+important used jboss project versions are listed below. You are
+encouraged to browse the individual project's documentation at and
+release notes at <a href="http://www.jboss.org">www.jboss.org</a>.<br>
<ul>
More information about the jboss-cvs-commits
mailing list