ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Conor MacNeill" <>
Subject Re: ejbjar does not include non-bean files
Date Wed, 20 Dec 2000 07:17:08 GMT

ejbjar does not include the support files by design. Whether that is right
or wrong, I'm not sure. I have always had a problem with support files. If
you go jar per bean but your support files are used by more than one bean,
what do you do? If you put it in each jar, well the potential classloader
conflicts scare me a little.

Dropping down to a weblogic specific level, I am pretty sure that weblogic
says something about support files, such as they are not supported by
hotdeploy. When I tried to package support classes under 4.51 I got a lot
of ClassNotFoundErrors. We have settled on building our ejb code into a jar
file which is deployed as a separate jar. We then package all the beans up,
one bean per jar. It may not be exactly what the EJB spec says, but it
works for now. We may revisit that but not in a hurry.

OK, so that is my particular situation and your's is no doubt different. If
you wanted to include additional class files into the jar, it would be
possible to add a <support-classes> nested element to select the support
classes with appropriate include / exclude classes. What do you think ?


----- Original Message -----
From: "Jeff Davies" <>
To: <>
Sent: Wednesday, December 20, 2000 11:09 AM
Subject: ejbjar does not include non-bean files

> Hi all!
>    I'm having a small problem building EJBs for Weblogic 5.1. For most of
> beans, Ant build the JAR files just fine. However, the problem I have has
> do with the inclusion of "utility" classes for the EJB. I have 2
> of files that need to go into my JAR file. They are in the following
> structure
> com.acme.*
> com.acme.utility.*
> When I invoke the ejbjar task, it does a great job finding all of the EBJ
> classes in the com.acme package, but it does not add the utility files
> non-ejb type files) in the com.acme.utility path to the JAR file.
> I suspect that the problem isn't the nested directory, but the fact that
> EJBJAR is reading the ejb-jar.xml file to figure out which .class files
> include in the JAR. Does anyone know a way around this, or am I doing
> something wrong?
> - Jeff Davies
>   Raving Ant lover!

View raw message