[Jboss-cvs] JBossAS SVN: r56481 - branches/Branch_4_0/build/docs
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Thu Aug 31 11:32:16 EDT 2006
Author: dimitris at jboss.org
Date: 2006-08-31 11:32:13 -0400 (Thu, 31 Aug 2006)
New Revision: 56481
Modified:
branches/Branch_4_0/build/docs/readme.html
Log:
Finished with 4.0.5.CR1 release notes
Modified: branches/Branch_4_0/build/docs/readme.html
===================================================================
--- branches/Branch_4_0/build/docs/readme.html 2006-08-31 15:15:32 UTC (rev 56480)
+++ branches/Branch_4_0/build/docs/readme.html 2006-08-31 15:32:13 UTC (rev 56481)
@@ -51,10 +51,6 @@
Replication for replicating http sessions. Note that this is *not* the
configured default, see
<a href="http://jira.jboss.com/jira/browse/JBAS-3297">JBAS-3297</a></li>
- <li>Our implementation of javax.management.timer.Timer (when running under
- jdk1.4) now supports fixed-delay periodic execution, in addition to
- fixed-rate, and this is now the default (<a href="http://jira.jboss.com/jira/browse/JBAS-3281">JBAS-3281</a>).
- This affects the schedule manager configuration, too (<a href="http://jira.jboss.com/jira/browse/JBAS-3282">JBAS-3282</a>).</li>
<li>The new <a href="http://www.jboss.org/wiki/Wiki.jsp?page=JBossWS">JBoss WebServices</a>
stack, has been updated to v1.0.3.GA, see the
<a href="http://jira.jboss.com/jira/secure/ConfigureReport.jspa?versions=12310844§ions=.1.7.2.4.6.9.8.3.5&style=text&selectedProjectId=12310050&reportKey=pl.net.mamut:releasenotes&Next=Next">
@@ -87,111 +83,37 @@
<a href="http://jira.jboss.com/jira/browse/JBAS-2904">JBAS-2904</a>.</li>
<li>HiLoKeyGenerator can now be used in a clustered setup,
<a href="http://jira.jboss.com/jira/browse/JBAS-3266">JBAS-3266</a>.</li>
+ <li>JNDIView MBean now shows the ENC of deployed web applications,
+ <a href="http://jira.jboss.com/jira/browse/JBAS-3547">JBAS-3547</a>.</li>
</ul>
<p>Plus more than 60 bug fixes, see the <a href="#Details">Detailed Release Notes</a>
section for the full details.</p>
<h2><a name="Compatibility">Compatibility Issues</a></h2>
-This lists the changes in 4.0.4.GA that could affect compatibility.
-
-<ul>
- <li>ScheduleProviders are now
- <a href="http://jira.jboss.com/jira/browse/JBAS-3082">cluster unaware</a>, in terms of class
- dependencies. The HASingleton attribute has been removed from the
- AbstractScheduleProviderMBean base interface, so in order to make them behave as cluster singletons, simply configure a
- dependency on <code>jboss.ha:service=HASingletonDeployer,type=Barrier</code>.</li>
- <li><a href="http://jira.jboss.com/jira/browse/JBAS-2651">Stable JSR77
- object names</a>, have been restored for EJBs. This reverts a previous
- change that put the jndi-name in the object name of the jsr77 mbean.</li>
- <li><a href="http://jira.jboss.com/jira/browse/JBAS-3062">
- org.jboss.tm.TxManager</a> has been deprecated. Use the
- org.jboss.tm.TransactionManagerLocator instead.</li>
- <li>Session replication cache is now
- <a href="http://jira.jboss.com/jira/browse/JBAS-3003">using the FD</a>
- (Failure Detection) protocol, in place of FD_SOCK.</li>
- <li>The xerces/xalan bundle have been updated to 2.7.1 / 2.7.0 respectively</li>
- <li>The IIOP subsystem logging is now
- <a href="http://jira.jboss.com/jira/browse/JBAS-2819">controlled by
- log4j.xml</a>, rather than jacorb.properties</li>
- <li>XMBean declared attributes cannot be
- <a href="http://jira.jboss.com/jira/browse/JBAS-1930">accessed as operations</a>
- anymore.</li>
- <li>Hibernate binary updated to 3.2.0.CR2, look at the
- <a href="http://sourceforge.net/project/shownotes.php?release_id=415073&group_id=40712">
- Relase Notes</a>.<p><strong>Impact:</strong></p>
-
-<ul>
- <li><strong>Hibernate 3.2.0.CR2 works with the latest ehcache v1.2 but not
- with previous versions. JBoss Portal v2.2.1 will fail to deploy on JBoss
- 4.0.4.GA unless ehcache gets upgraded to v1.2.</strong></li>
- <li><strong>For non-transactional access,
- accessing the session outside the scope of a transaction has slightly
- different semantics in certain situations then in earlier versions. Two
- changes in particular are significant, but we feel much more correct.
- First, with FlushMode.AUTO, when a query is executed, Hibernate flushes
- any pertinent changes pending in the session to ensure correct query
- results. Starting with 3.2, this is no longer the case if we are
- outside a transaction; in that case the auto flush is skipped. Second
- has to do with identifiers generated via an "in-database" strategy (the
- so-called post-insert id generators). Saves to such entities in
- previous versions caused an immediate SQL INSERT to be issued in order
- to determine the generated identifier value. Starting with 3.2, these
- INSERTS will be delayed when done outside of a transaction (note this
- is planned, but not yet implemented).</strong>.
- </li>
-</ul>
-
- </li>
- <li>The EJB3 RC7+ preview has been updated to match the current EJB3 draft
- and a number of incompatible changes have occurred in the spec. See
+This lists the changes that could affect compatibility.<ul>
+ <li>The web container is now configured by default to abort any active
+ transactions at the end of a request. This is the Java EE specified
+ behavior, but it can be turned-off, if necessary,
+ <a href="http://jira.jboss.com/jira/browse/JBAS-3242">JBAS-3242</a>.</li>
+ <li>Our implementation of javax.management.timer.Timer (when running under
+ jdk1.4) now supports fixed-delay periodic execution in addition to
+ fixed-rate, and this is now the default (<a href="http://jira.jboss.com/jira/browse/JBAS-3281">JBAS-3281</a>)
+ for the JMX timer. This affects the schedule manager (<a href="http://jira.jboss.com/jira/browse/JBAS-3282">JBAS-3282</a>)
+ and the TimerService (<a href="http://jira.jboss.com/jira/browse/JBAS-3391">JBAS-3391</a>
+ that now have an additional FixedRate attribute to establish the old
+ fixed-rate behavior.</li>
+ <li>The EJB3 preview has been updated to match the current EJB3 draft. See
<a href='http://www.jboss.com/wiki/Wiki.jsp?page=EJB3'>EJB3 Wiki</a> for a
- list of the documented issues.<p><strong>Impact: <font color="#FF0000">EJB deployments generally will have
- to be updated to conform to the spec changes.</font></strong>.</p></li>
- <li>JBoss webservices updated to the new JBossWS stack. See
- <a href='http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossWS'>JBossWS</a>
- for FAQs, comparison of the old and new stack.
- <p><strong>Impact: <font color="#FF0000">See
- <a href='http://wiki.jboss.org/wiki/Wiki.jsp?page=JBoss404WSCompatibility'>JBoss404WSCompatibility</a>
- for a list of the known compatibility issues.</font></strong></p></li>
- <li>Upgrade to javassist 3.2.0.CR2. <strong>Impact: <font color="#FF0000">There is at least one incompatible.
- signature change. The CtClass.stopPruning(boolean) method return type
- changed from void to boolean.</font></strong>.
- </li>
- <li>Tomcat updated to version 5.5.17. See
- the
- <a href='http://mirrors.ibiblio.org/pub/mirrors/apache/tomcat/tomcat-5/v5.5.17/RELEASE-NOTES'>Release Notes</a>.<p><strong>Impact: None known</strong> </p></li>
+ list of the documented issues.</li>
</ul>
-
-<h2><a name="Configuration">Configuration Issues</a></h2>
-This lists the changes in 4.0.4.GA that could affect configuration.<ul>
+<h2><a name="Configuration">Configuration Issues</a></h2>This lists the changes that could affect configuration.<ul>
<li>The JBossAS distributions now include the installer (.jar), the sources
(.tar.gz) and the canonical binary release (.zip). Unzipping the binary
distribution (.zip) with a native unzip utility will restore correctly the
executable permission in the /bin/*.sh files. However, unzipping using the
JDK jar utility ignores the executable bit, so this need to be set manually.</li>
- <li>Clustered Services now use
- <a href="http://wiki.jboss.org/wiki/Wiki.jsp?page=SimplifiedClusteredServiceConfig">
- injection of the ClusterPartition</a>, but the old JNDI-based lookup mode is
- also supported.</li>
- <li>A <a href="http://jira.jboss.com/jira/browse/JBAS-3050">potential
- deadlock</a> in the restart of a URLDeploymentScanner is solved with the
- introduction of a configurable timeout, set by default to 60 secs.</li>
- <li>A <a href="http://jira.jboss.com/jira/browse/JBAS-3041">
- org.jboss.mx.loading.blacklistMode</a> system property has been added to
- control the blacklisting optimization in the JBoss ClassLoader.</li>
- <li>The <a href="http://jira.jboss.com/jira/browse/JBAS-1023">JARDeployer</a>
- will now accept explicit deployment suffixes (.jar, .zip, .last) and
- non-dotted deployments (e.g. deploy-hasingleton)</li>
- <li>The functionality for
- <a href="http://jira.jboss.com/jira/browse/JBAS-2483">restarting jboss </a>
- with "jboss.system:type=Server -> exit|halt(10) has been restored</li>
- <li>There is a new system
- <a href="http://jira.jboss.com/jira/browse/JBAS-2574">start-up script for
- HP-UX</a> (bin/jboss_init_hpux.sh).</li>
- <li>The run.bat/run.conf scripts were updated to set
- <a href="http://jira.jboss.com/jira/browse/JBAS-2937">RMI Distributed
- Carbage Collection interval to 1h</a> (it's 1 minute by default). This is
- when running under a Sun JDK. The min/max heap size is now set to 128m/512m
- respectively.</li>
+ <li>The -server flag is not supported by the IBM JVM, so it now
+ conditionally set by the run.sh/run.bat scripts,
+ <a href="http://jira.jboss.com/jira/browse/JBAS-3458">JBAS-3458</a>.</li>
</ul>
<p>Note that as of the 4.0.1 release, the distributed configurations have
switched back to the 3.2.x types of distribution configurations:</p>
@@ -271,7 +193,6 @@
<li>apache-xmlsec, upgraded to v1.3.0 (from v1.2.97)</li>
<li>jacorb, upgraded to v2.2.4jboss-patch1 (from v2.2.3)</li>
<li>sun-jaf, upgraded to v1.1 (from v1.0.2)</li>
- <li>sun-jaxb, introduced at v2.0</li>
<li>sun-javamail, upgraded to v1.4 (from 1.3.1)</li>
</ul>
More information about the jboss-cvs-commits
mailing list