Version @VERSION@
-$Id: ejb.html,v 1.11 2001/10/30 10:05:38 bodewig Exp $
+$Id: ejb.html,v 1.12 2001/11/19 18:51:48 cyrille Exp $
The <jonas> nested element is used to build JOnAS-specific stubs + and skeletons and construct a JAR file which may be deployed to the JOnAS + Application Server. The build process will always determine if the EJB +stubs/skeletons and the EJB-JAR file are up to date, and it will do the +minimum amount of work required.
+Like the WebLogic element, a naming convention for the EJB descriptors + is most commonly used to specify the name for the completed JAR file. For + example, if the EJB descriptor ejb/Account-ejb-jar.xml is found in the descriptor + directory, the iplanet element will search for an JOnAS-specific EJB descriptor + file named ejb/jonas-Account-jar.xml (if it isn't found, the task will fail) + and a JAR file named ejb/Account.jar will be written in the destination +directory. Note that when the EJB descriptors are added to the JAR file, +they are automatically renamed META-INF/ejb-jar.xml and META-INF/jonas-ejb-jar.xml. +But please , be careful the name is jonas-Account-jar.xml and not Account-jonas-ejb-jar.xml. + The task uses JOnAS convention naming.
+Of course, this naming behavior can be modified by specifying attributes + in the ejbjar task (for example, basejarname, basenameterminator, and flatdestdir) + as well as the iplanet element (for example, suffix). Refer to the appropriate + documentation for more details.
+| 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
+ + |
+
| 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. Note that nested "classpath" elements + may also be used. | +No | +
| keepgenerated | +Indicates whether or not the Java source files which + are generated by gewill be saved or automatically deleted. If "yes", the +source files will be retained. If omitted, it defaults to "no". | +No | +
| orb + |
+ Choose your ORB : RMI, JEREMIE, DAVID, ... If omitted, it defaults
+to the one present in 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 ejbc 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 '*-ejb-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="**/*-ejb-jar.xml"/>
+ <exclude name="**/jonas-*-jar.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 not 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}" suffix=".jar"
+ classpath="${descriptorbuild.classpath}" />
+ <include name="**/ejb-jar.xml"/>
+ <exclude name="**/jonas-ejb-jar.xml"/>
+ </ejbjar>
+