ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Conor MacNeill" <>
Subject Re: problem with ejbjar including base class also in the jar file
Date Sun, 25 Mar 2001 13:17:43 GMT

Currently there is no way to avoid this(*). The jars are supposed to be
relatively self contained and this is why they include the superclass and
superinterfaces. The EJB spec says this (section 17.3)

The ejb-jar file must also contain the class files for all the classes and
interfaces that the enterprise bean
class, and the remote and home interfaces depend on. This includes their
superclasses and superinter-faces,
and the classes and interfaces used as method parameters, results, and

Now, ejbjar does that for superclasses and super interfaces but not for all
classes. Like you I have a number of support classes (not actually
superclasses) that I bundle into a separate jar. We could make it an option
for the task but can you tell me if it is actually a problem as is.

* There is one way to avoid this and that is to ensure the super class is
not in the classpath given to ejbjar. Not a great workaround.


----- Original Message -----
From: "Nilesh Shah" <>
To: <>
Sent: Wednesday, March 07, 2001 7:56 AM
Subject: problem with ejbjar including base class also in the jar file

> I have following EJB classes -
> - the remote interface
> - the home interface
> - the implementation class
> now, the extends
> When I run ejbjar task with ant, it builds the jar fine, but it also
> adds BeanBase.class to the jar file. I have a problem with that because
> that class is part of another base jar file and I don't want to have
> multiple copies of the class in multiple jar files. Is there something I
> can do for ant to avoid putting the super class in the jar file?
> thanks in advance
> Nilesh
> p.s: I'm using ant 1.3 with  ejbjar task with weblogic 5.1

View raw message