[jboss-cvs] JBossAS SVN: r66141 - branches/Branch_4_2/build/docs.

[jboss-cvs-commits at lists.jboss.org]

Author: dimitris at jboss.org
Date: 2007-10-15 17:54:44 -0400 (Mon, 15 Oct 2007)
New Revision: 66141

Modified:
   branches/Branch_4_2/build/docs/readme.html
Log:
JBAS-4695, release notes for 4.2.2.GA, more info on jbossxb and jbossws

Modified: branches/Branch_4_2/build/docs/readme.html
===================================================================
--- branches/Branch_4_2/build/docs/readme.html	2007-10-15 19:54:10 UTC (rev 66140)
+++ branches/Branch_4_2/build/docs/readme.html	2007-10-15 21:54:44 UTC (rev 66141)
@@ -121,7 +121,13 @@
 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&nbsp;2.0.1 used in AS 4.2.2 provides
-full JAX-WS support. If you have used in your code the&nbsp;annotation <span style="font-family: monospace;">org.jboss.ws.annotation.WebContext</span>&nbsp;this must&nbsp;be&nbsp;replaced by <span style="font-family: monospace;">org.jboss.wsf.spi.annotation.WebContext.</span></li><li>Finding
+full JAX-WS support. If you have used in your code the&nbsp;annotation <span style="font-family: monospace;">org.jboss.ws.annotation.WebContext</span>&nbsp;this must&nbsp;be&nbsp;replaced by <span style="font-family: monospace;">org.jboss.wsf.spi.annotation.WebContext.</span></li><li>JBoss
+WS 1.0.x&nbsp;due to a deployer limitation used a proprietary .jse
+extension&nbsp;for deploying WS endpoints&nbsp;nested in .sar files.
+This was deprecated with JBoss WS 1.2.x. and with JBoss WS 2.x this
+proprietary extention is not supported anymore as it is possible to use
+the standard&nbsp;.war extension for deploying nested WS endpoints. If
+you seeINIT_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>Finding
 the default local business interface on a ejb3 bean may not work in
 certain inheritance scenarios. You may workaround this known
 problem&nbsp;by&nbsp;annotating the local business interface. Read more
@@ -272,7 +278,7 @@
 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>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