From 3bad2ab3a00a5aecae4172d6f4ee8e7e87c820f8 Mon Sep 17 00:00:00 2001
From: Conor MacNeill
In addition to the bean classes, ejbjar is able to ad additional classes to the generated +ejbjar. These classes are typically the support classes which are used by the bean's classes or as +parameters to the bean's methods.
+ +In versions of Ant prior to 1.5, ejbjar used reflection and attempted to add the super +classes and super interfaces of the bean classes. For this technique to work the bean +classes had to be loaded into Ant's JVM. This was not always possible due to class dependencies. +
+ +The ejbjar task in Ant 1.5 uses the jakarta-BCEL library to analyze the bean's class +files directly, rather than loading them into the JVM. This also allows ejbjar to add all +of the required support classes for a bean and not just super classes. +
+ +In Ant 1.5, a new attribute, dependency
has been introduced to allow the
+buildfile to control what additional classes are added to the generated jar. It takes three
+possible values
none
- only the bean classes and interfaces described in the bean's
+descriptor are added to the jar.super
- this is the default value and replicates the original ejbjar
+behaviour where super classes and super interfaces are added to the jarfull
- In this mode all classes used by the bean's classes and interfaces
+are added to the jarThe super
and full
values require the jakarta-BCEL library
+to be available. If it is not, ejbjar will drop back to the behaviour corresponding to
+the value none
.
No. | ||
dependency | +This attribute controls which additional classes and interfaces + are added to the jar. Please refer to the description + above | +No. | +