[jboss-cvs] JBossAS SVN: r75550 - branches/Branch_4_2/build/docs.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Wed Jul 9 09:49:22 EDT 2008
Author: dimitris at jboss.org
Date: 2008-07-09 09:49:21 -0400 (Wed, 09 Jul 2008)
New Revision: 75550
Modified:
branches/Branch_4_2/build/docs/readme.html
Log:
JBAS-5748, Update links in ROOT.war/index.html
Modified: branches/Branch_4_2/build/docs/readme.html
===================================================================
--- branches/Branch_4_2/build/docs/readme.html 2008-07-09 13:46:28 UTC (rev 75549)
+++ branches/Branch_4_2/build/docs/readme.html 2008-07-09 13:49:21 UTC (rev 75550)
@@ -1,6 +1,7 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html><head><!-- $Id: readme.html,v 1.1.2.36 2006/05/13 15:42:36 dimitris Exp $ -->
-<meta content="text/html" http-equiv="content-type"><meta content="JBoss Inc." name="author"><title>JBoss 4.2.2.GA Readme</title></head>
+<meta content="text/html" http-equiv="content-type"><meta content="JBoss Inc." name="author"><title>JBoss
+4.2.2.GA Readme</title></head>
<body><a href="http://www.jboss.com"><img src="http://www.jboss.org/themes/jbosstheme/img/logo.gif" alt="JBoss Inc."></a><h1>JBoss AS 4.2.2.GA
Release Notes</h1>
<p>This is the second bug fixing release of the <a href="http://labs.jboss.org/jbossas/">JBoss Application
@@ -102,7 +103,10 @@
scoped deployment.</li>
</ul><h3>Minor feature additions in 4.2.2.GA</h3><ul><li>The
most promiment feature addition is full support for JAX-WS by upgrading
-to JBoss WS 2.x. See the release notes <a href="http://labs.jboss.org/file-access/default/members/jbossws/downloads/ReleaseNotes-2.0.1.GA.txt">here</a>. You may also find useful information in the <a href="http://jbws.dyndns.org/mediawiki/index.php?title=Quick_Start">Quick Start</a> or the <a href="http://jbws.dyndns.org/mediawiki/index.php?title=JAX-WS_User_Guide">JAX-WS User Guide</a>.</li><li>A
+to JBoss WS 2.x. See the release notes <a href="http://labs.jboss.org/file-access/default/members/jbossws/downloads/ReleaseNotes-2.0.1.GA.txt">here</a>.
+You may also find useful information in the <a href="http://jbws.dyndns.org/mediawiki/index.php?title=Quick_Start">Quick
+Start</a> or the <a href="http://jbws.dyndns.org/mediawiki/index.php?title=JAX-WS_User_Guide">JAX-WS
+User Guide</a>.</li><li>A
new tomcat filter for flushing the jboss authentication cache upon
session expiration, <a href="http://jira.jboss.com/jira/browse/JBAS-4752">JBAS-4752</a>.</li></ul><h3>Minor
feature additions in 4.2.1.GA<br>
@@ -119,22 +123,33 @@
the individual <a href="readme.html#Libraries">JBoss
and Thirdparty libraries</a> updated with this release. Some
related issues that you should be aware of are listed below:<br>
-<h3>JBossAS 4.2.2.GA</h3><ul><li>JBossWS 1.2.1 supported JAX-WS only as
-a technology preview while JBossWS 2.0.1 used in AS 4.2.2 provides
-full JAX-WS support. If you have used in your code the annotation <span style="font-family: monospace;">org.jboss.ws.annotation.WebContext</span> this must be replaced by <span style="font-family: monospace;">org.jboss.wsf.spi.annotation.WebContext.</span></li><li>JBoss
+<h3>JBossAS 4.2.2.GA</h3><ul><li>JBossWS 1.2.1
+supported JAX-WS only as
+a technology preview while JBossWS 2.0.1 used in AS 4.2.2
+provides
+full JAX-WS support. If you have used in your code
+the annotation <span style="font-family: monospace;">org.jboss.ws.annotation.WebContext</span> this
+must be replaced by <span style="font-family: monospace;">org.jboss.wsf.spi.annotation.WebContext.</span></li><li>JBoss
WS 1.0.x due to a deployer limitation used a proprietary .jse
-extension for deploying WS endpoints nested in .sar files.
+extension for deploying WS endpoints nested in .sar
+files.
This was deprecated with JBoss WS 1.2.x. and with JBoss WS 2.x this
proprietary extension is not supported anymore as it is possible to use
-the standard .war extension for deploying nested WS endpoints. If
-you see: INIT_WAITING_DEPLOYER error messages for .jse files, re-package them using a .war extension, <a href="http://jira.jboss.com/jira/browse/JBWS-1854">JBWS-1854</a>.<span style="font-family: monospace;"></span></li><li>Another
-known limitation is that EJB3 web service endpoints can only be
+the standard .war extension for deploying nested WS endpoints.
+If
+you see: INIT_WAITING_DEPLOYER error messages for .jse files,
+re-package them using a .war extension, <a href="http://jira.jboss.com/jira/browse/JBWS-1854">JBWS-1854</a>.<span style="font-family: monospace;"></span></li><li>Another
+known limitation is that EJB3 web service endpoints can only
+be
specified using annotations and not metadata in jboss.xml. This is
-something that will be addressed in a future release, <a href="http://jira.jboss.com/jira/browse/JBAS-4852">JBAS-4852</a>, <a href="http://jira.jboss.com/jira/browse/JBWS-1813">JBWS-1813</a>.</li><li>Finding
+something that will be addressed in a future release, <a href="http://jira.jboss.com/jira/browse/JBAS-4852">JBAS-4852</a>,
+<a href="http://jira.jboss.com/jira/browse/JBWS-1813">JBWS-1813</a>.</li><li>Finding
the default local business interface on a ejb3 bean may not work in
certain inheritance scenarios. You may workaround this known
-problem by annotating the local business interface. Read more
-about this at <a href="http://jira.jboss.com/jira/browse/EJBTHREE-1062">EJBTHREE-1062</a>.<span style="font-family: monospace;"><br></span></li><li>EJB Timer
+problem by annotating the local business interface.
+Read more
+about this at <a href="http://jira.jboss.com/jira/browse/EJBTHREE-1062">EJBTHREE-1062</a>.<span style="font-family: monospace;"><br></span></li><li>EJB
+Timer
related fixes, <a href="http://jira.jboss.com/jira/browse/JBAS-3379">JBAS-3379</a>,
<a href="http://jira.jboss.com/jira/browse/JBAS-4053">JBAS-4053</a>.</li><li>JBossMQ
related fixes, JBAS-4525, JBAS-4555, JBAS-4559, JBAS-4607, JBAS-4625,
@@ -142,11 +157,14 @@
source code by default, <a href="http://jira.jboss.com/jira/browse/JBAS-4605">JBAS-4605</a>.</li><li>The
mail-ra.rar resource adapter was missing from the distro, <a href="http://jira.jboss.com/jira/browse/JBAS-4659">JBAS-4659</a>.</li><li>HSQLDB
(which shouldn't be used in production) v1.8.0.8 has a known bug when
-used in server mode, <a href="http://jira.jboss.com/jira/browse/JBAS-4694">JBAS-4694</a>. This doesn't affect the default jboss installation where HSQLDB is used in in-process mode.</li><li>Serialization
+used in server mode, <a href="http://jira.jboss.com/jira/browse/JBAS-4694">JBAS-4694</a>.
+This doesn't affect the default jboss installation where HSQLDB is used
+in in-process mode.</li><li>Serialization
of HomeHandleImplIIOP has changed. In the unlikely case of a
compatibility problem, define the system property
-Dorg.jboss.proxy.ejb.old.homehandle.serialization=true to fall back to
-the legacy serialization mode, <a href="http://jira.jboss.com/jira/browse/JBAS-4801">JBAS-4801</a>. </li></ul><h3>JBossAS
+the legacy serialization mode, <a href="http://jira.jboss.com/jira/browse/JBAS-4801">JBAS-4801</a>.
+</li></ul><h3>JBossAS
4.2.1.GA
</h3><ul><li>JBoss TS, the new default transaction
manager will not let
@@ -281,7 +299,8 @@
remoting upgraded to v2.2.2.SP1 (from v2.2.1.GA)</li><li>jboss
ts upgraded to v4.2.3.SP6 (from v4.2.3.SP5)</li><li>jboss
web upgraded to v2.0.1.GA (from v2.0.0.GA)</li><li>jboss ws
-upgraded to v2.0.1.SP2 (from v1.2.1.GA)</li><li>jboss xb upgraded to v1.0.0.SP1 (from v1.0.0.GA)</li><li>jgroups
+upgraded to v2.0.1.SP2 (from v1.2.1.GA)</li><li>jboss xb
+upgraded to v1.0.0.SP1 (from v1.0.0.GA)</li><li>jgroups
upgraded to v2.4.1.SP4 (from v2.4.1.SP3)</li></ul>Thirdparty
Library Updates
<ul><li>hsqldb upgraded to v1.8.0.8 (from v1.8.0.2)</li><li>jacorb
@@ -509,18 +528,20 @@
- Update the release notes for JBossAS 4.2.1.GA</li>
<li>[<a href="http://jira.jboss.com/jira/browse/JBAS-4510">JBAS-4510</a>]
- Upgrade jboss remoting to v2.2.1.GA (from v2.2.0.SP4)</li>
-</ul><!-- ======================================================= --><h2><a name="Documentation">Documentation
-and Help</a></h2>The <a href="http://labs.jboss.org/jbossas/">JBossAS community
-project</a> is hosted on jboss.org labs. Documentation and help
+</ul><!-- ======================================================= --><hr><h2><a name="Documentation">Documentation
+and Help</a></h2>The <a href="http://www.jboss.org/jbossas/">JBossAS community
+project</a> is hosted on jboss.org . Documentation and help
may
be obtained from the following locations.
-<ul><li><a href="http://labs.jboss.org/jbossas/docs">JBoss
+<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.org/">JBoss JIRA</a></li>
+<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>
-</ul><!-- ======================================================= --><h2><a name="Licenses">Licenses</a></h2>
+</ul>
+<!-- ======================================================= --><h2><a name="Licenses">Licenses</a></h2>
<p>JBoss Application Server is licensed under the <a href="lgpl.html">LGPL</a>,
as explained in the <a href="JBossORG-EULA.txt">JBoss End
User License Agreement</a>. The licence texts for JBoss and the
More information about the jboss-cvs-commits
mailing list