You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ant.apache.org by co...@apache.org on 2003/02/16 14:02:26 UTC
cvs commit: ant/docs/manual/OptionalTasks ejb.html
conor 2003/02/16 05:02:26
Modified: docs/manual/OptionalTasks ejb.html
Log:
Document that <ejbjar> supports EJB 2.0 descriptors
PR: 12830
Revision Changes Path
1.31 +4 -4 ant/docs/manual/OptionalTasks/ejb.html
Index: ejb.html
===================================================================
RCS file: /home/cvs/ant/docs/manual/OptionalTasks/ejb.html,v
retrieving revision 1.30
retrieving revision 1.31
diff -u -w -u -r1.30 -r1.31
--- ejb.html 25 Oct 2002 08:00:20 -0000 1.30
+++ ejb.html 16 Feb 2003 13:02:26 -0000 1.31
@@ -530,8 +530,8 @@
<h2><a name="ejbjar">ejbjar</a></h2>
<h3><b>Description:</b></h3>
-<p>This task is designed to support building of EJB1.1 jar files. Support is
-currently provided for 'vanilla' EJB1.1 jar files - i.e. those containing only
+<p>This task is designed to support building of EJB jar files (EJB 1.1 & 2.0).
+Support is currently provided for 'vanilla' EJB jar files - i.e. those containing only
the user generated class files and the standard deployment descriptor. Nested
elements provide support for vendor specific deployment tools. These currently
include: </p>
@@ -548,7 +548,7 @@
<p>The task works as a directory scanning task, and performs an action for each
deployment descriptor found. As such the includes and excludes should be set
-to ensure that all desired EJB1.1 descriptors are found, but no application
+to ensure that all desired EJB descriptors are found, but no application
server descriptors are found. For each descriptor found, ejbjar will parse the
deployment descriptor to determine the necessary class files which implement the
bean. These files are assembled along with the deployment descriptors into a