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

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

Author: dimitris at jboss.org
Date: 2007-10-17 08:50:28 -0400 (Wed, 17 Oct 2007)
New Revision: 66216

Modified:
   branches/Branch_4_2/build/docs/readme.html
Log:
JBAS-4695, release notes for 4.2.2.GA, more info on ejb3/ws service endpoint overrides.

Modified: branches/Branch_4_2/build/docs/readme.html
===================================================================
--- branches/Branch_4_2/build/docs/readme.html	2007-10-17 12:39:07 UTC (rev 66215)
+++ branches/Branch_4_2/build/docs/readme.html	2007-10-17 12:50:28 UTC (rev 66216)
@@ -127,7 +127,10 @@
 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:&nbsp;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>Finding
+you see:&nbsp;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&nbsp;EJB3 web service endpoints can only be
+specified using annotations and not metadata in jboss.xml. This is
+something that will be addressed&nbsp;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&nbsp;by&nbsp;annotating the local business interface. Read more