Daniel,
this is an example of the new style ejbjar task.
<ejbjar srcdir="../../compile"
descriptordir="../../compile/de/sitewaerts/futuna/ejb/entity"
basejarname="futunaentity">
<weblogic destdir="../../application/fbs/serverclasses/temp"
oldCMP="false" rebuild="false" compiler="jikes">
<classpath>
<path refid="base_classpath"/>
<pathelement path="../../compile"/>
</classpath>
</weblogic>
<include name="**/ejb-jar.xml"/>
<exclude name="**/weblogic*.xml"/>
</ejbjar>
The descriptors are ejb-jar.xml, weblogic-ejb-jar.xml and the bunch of
weblogic-cmp-rdbms-jar-<entityname>.xml files, all located in
'../../compile/de/sitewaerts/futuna/ejb/entity'.
The srcdir is the directory where the compiled classes are located.
The descriptordir points to the directory where the descriptors are actually
located.
The basejarname attribute is the actual name of the resulting jar
(futunaentity.jar in this case).
the attribute 'rebuild="false"' causes the weblogic task to run ejbc just in
case that interfaces of ejbs have been changed. Otherwise just the modified
bean class is replaced in the jar.
Daniel
