@@ -107,7 +107,8 @@ is based on the standard Ant include and exclude selection mechanisms.
</tr>
</table>
<h3>Examples</h3>
<pre><ddcreator descriptors="${dd.dir}"
<pre>
<ddcreator descriptors="${dd.dir}"
dest="${gen.classes}"
classpath="${descriptorbuild.classpath}">
<include name="*.txt"/>
@@ -177,7 +178,8 @@ or are out of date, the ejbc tool is run to generate new versions.</p>
</tr>
</table>
<h3>Examples</h3>
<pre><ejbc descriptors="${gen.classes}"
<pre>
<ejbc descriptors="${gen.classes}"
src="${src.dir}"
dest="${gen.classes}"
manifest="${build.manifest}"
@@ -291,7 +293,8 @@ directory. If omitted, the ejbc utility must be on the user's system path. </td>
<h3>
Examples</h3>
<pre><iplanet-ejbc ejbdescriptor="ejb-jar.xml"
<pre>
<iplanet-ejbc ejbdescriptor="ejb-jar.xml"
iasdescriptor="ias-ejb-jar.xml"
dest="${build.classesdir}"
classpath="${ias.ejbc.cpath}"/>
@@ -1361,8 +1364,8 @@ the classpath of the ejbdeploy tool and set the <i>websphere.home</i> property (
in the descriptor dir:</p>
<pre>
<property name="webpshere.home" value="${was4.home}"/>
<ejbjar srcdir="${build.class}" descriptordir="etc/ejb">
<property name="webpshere.home" value="${was4.home}"/>
<ejbjar srcdir="${build.class}" descriptordir="etc/ejb">
<include name="*-ejb-jar.xml"/>
<websphere dbvendor="DB2UDBOS390_V6"
ejbdeploy="true"
@@ -1377,9 +1380,9 @@ in the descriptor dir:</p>
<pathelement location="${was4.home}/lib/j2ee.jar"/>
<pathelement location="${was4.home}/lib/vaprt.jar"/>
</wasclasspath>
<classpath>
<path refid="build.classpath"/>
</classpath>
<classpath>
<path refid="build.classpath"/>
</classpath>
</websphere>
<dtd publicId="-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 1.1//EN"
location="${lib}/dtd/ejb-jar_1_1.dtd"/>
@@ -1491,7 +1494,8 @@ This example demonstrates the typical use of the <code><iplanet></code> ne
It will name each EJB-JAR using the "basename" prepended to each standard
EJB descriptor. For example, if the descriptor named "Account-ejb-jar.xml"
is processed, the EJB-JAR will be named "Account.jar"
<pre> <ejbjar srcdir="${build.classesdir}"
<pre>
<ejbjar srcdir="${build.classesdir}"
descriptordir="${src}">
<iplanet destdir="${assemble.ejbjar}"
@@ -1502,7 +1506,8 @@ is processed, the EJB-JAR will be named "Account.jar"
This example demonstrates the use of a nested classpath element as well
as some of the other optional attributes.
<pre> <ejbjar srcdir="${build.classesdir}"
<pre>
<ejbjar srcdir="${build.classesdir}"
descriptordir="${src}">
<iplanet destdir="${assemble.ejbjar}"
@@ -1522,7 +1527,8 @@ This example demonstrates the use of basejarname attribute. In this
case, the completed EJB-JAR will be named "HelloWorld.jar" If multiple
EJB descriptors might be found, care must be taken to ensure that the completed
JAR files don't overwrite each other.
<pre> <ejbjar srcdir="${build.classesdir}"
<pre>
<ejbjar srcdir="${build.classesdir}"
descriptordir="${src}"
basejarname="HelloWorld">
@@ -1536,7 +1542,8 @@ copies of the DTDs are included in the classpath, they will be automatically
referenced without the nested elements. In iAS 6.0 SP2, these local DTDs are
found in the [iAS-install-directory]/APPS directory. In iAS 6.0 SP3, these
local DTDs are found in the [iAS-install-directory]/dtd directory.
<pre> <ejbjar srcdir="${build.classesdir}"
<pre>
<ejbjar srcdir="${build.classesdir}"
descriptordir="${src}">
<iplanet destdir="${assemble.ejbjar}">
classpath="${ias.ejbc.cpath}"/>