From 334597d246c97f709d92d2be9c417d8d4dca4a96 Mon Sep 17 00:00:00 2001
From: Conor MacNeill Version @VERSION@ Ant provides a number of optional tasks for developing
-Enterprise Java Beans (EJBs)
-. In general these tasks are specific to the particular vendor's EJB Server.
@@ -32,11 +33,10 @@ $Id$
Introduction
At present the tasks support:
-
Ant provides a number of optional tasks for developing -Enterprise Java Beans (EJBs). -In general these tasks are specific to the particular vendor's EJB Server. At present the tasks support -Weblogic 4.5.1 and 5.1 EJB servers. Over time we expect further optional tasks -to support additional EJB Servers.
+| ddcreator | Weblogic 4.5.1 | |
| ejbc | Weblogic 4.5.1 | |
| iplanet-ejbc | iPlanet Application Server 6.0 | |
| ejbjar | Nested Elements | |
| ejbjar | Nested Elements | |
| borland | Borland Application Server 4.5 | |
| jBoss | jBoss | |
| iPlanet | iPlanet Application Server 6.0 | |
| weblogic | Weblogic 5.1 & 6.0 | |
| jonas | JOnAS 2.4 | |
| wlrun | Weblogic 4.5.1, 5.1 & 6.0 | |
| wlstop | Weblogic 4.5.1, 5.1 & 6.0 | |
| Attribute | +Description | +Required | +
| destdir | +The base directory into which the generated JAR files + will be written. Each JAR file is written in directories which correspond + to their location within the "descriptordir" namespace. | +Yes | +
| jonasroot + |
+ The root directory for JOnAS. + |
+
+ Yes
+ + |
+
| workdir + |
+ The work directory to use. Specify where to place
+the generated files, before to add to the jar. The directory should be empty.
+If omitted, it defaults to a temporary directory. + |
+
+ No
+ + |
+
| cleanworkdir + |
+ Clean the working directory after work.
+ If omitted, it defaults to false, but your jar will contain
+ wrong files if you don't clean the workdir yourself. + Temporary working directory is always cleaned. + |
+
+ No
+ + |
+
| classpath | +The classpath used when generating EJB stubs and skeletons. + If omitted, the classpath specified in the "ejbjar" parent task will + be used. If specified, the classpath elements will be prepended to the + classpath specified in the parent "ejbjar" task (see also the ORB + attribute documentation below). Note that nested "classpath" elements + may also be used. | +No | +
| keepgenerated | +Indicates whether or not the Java source files which + are generated by GenIC will be saved or automatically deleted. If "yes", the +source files will be retained. If omitted, it defaults to "no". | +No | +
| keepgeneric | +This controls whether the generic file used as input to + GenIC is retained. | +No, defaults to false | +
| secpropag | +Modify the RMI Skel. and Stub. to implement the + implicit propagation of the security context (note that + the transactionnal context is always provided). + | +No, defaults to false. | +
| orb + |
+ Choose your ORB : RMI, JEREMIE, DAVID, ... If omitted, it defaults
+to the one present in classpath. If specified, the corresponding JOnAS JAR is
+automatically added to the classpath. + |
+ No | +
| noGENIC + |
+ If this attribute is set to true, JOnAS's GenIC will + not be run on the EJB jar. Use this if you prefer to + run GenIC at deployment time. | +
+ No
+ |
+
| suffix | +String value appended to the JAR filename when creating each JAR. + If omitted, it defaults to ".jar". | +No | +
| verbose + |
+ Indicates whether or not to use -verbose switch. If +omitted, it defaults to "no". | +
+ No
+ + |
+
| compiler + |
+ This allows for the selection of a different compiler
+ to be used for the compilation of the generated Java
+ files. This could be set, for example, to Jikes to
+ compile with the Jikes compiler. If this is not set
+ and the build.compiler property is set
+ to jikes, the Jikes compiler will be used. If this
+ is not desired, the value "default"
+ may be given to use the default compiler+ |
+
+ No
+ + |
+
| args + |
+ Add additional args to GenIC. + |
+
+ No
+ + |
+
As noted above, the jonas element supports additional <classpath> + nested elements.
+This example shows ejbjar being used to generate deployment jars using + a JOnAS EJB container. This example requires the naming standard to be + used for the deployment descriptors. Using this format will create a ejb + jar file for each variation of '*-jar.xml' that is found in the +deployment descriptor directory.
+
+ <ejbjar srcdir="${build.classes}"
+ descriptordir="${descriptor.dir}">
+ <jonas destdir="${deploymentjars.dir}"
+ jonasroot="${jonas.root}"
+ orb="RMI" />
+ <include name="**/*.xml"/>
+ <exclude name="**/jonas-*.xml"/>
+ <support dir="${build.classes}">
+ <include name="**/*.class"/>
+ </support>
+ </ejbjar>
+
+
+This example shows ejbjar being used to generate a single deployment jar + using a JOnAS EJB container. This example does require the deployment + descriptors to use the naming standard. This will create only one ejb jar + file - 'TheEJBJar.jar'.
+
+ <ejbjar srcdir="${build.classes}"
+ descriptordir="${descriptor.dir}"
+ basejarname="TheEJBJar">
+ <jonas destdir="${deploymentjars.dir}"
+ jonasroot="${jonas.root}"
+ suffix=".jar"
+ classpath="${descriptorbuild.classpath}" />
+ <include name="**/ejb-jar.xml"/>
+ <exclude name="**/jonas-ejb-jar.xml"/>
+ </ejbjar>
+
Copyright © 2001 Apache Software Foundation. All rights Reserved.
+ +