problem with ejbjar including base class also in the jar file

[Nilesh Shah <nm...@yahoo.com>]

I have following EJB classes -

Company.java - the remote interface
CompanyHome.java - the home interface
CompanyBean.java - the implementation class

now, the CompanyBean.java extends BeanBase.java

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

Re: problem with ejbjar including base class also in the jar file

[Nilesh Shah <nm...@yahoo.com>]

Conor,

It would be great if adding super classes and interfaces is optional.
That would help me to maintain compatibility with our old ejb-jar 
structures and still be able to convince my colleagues to migrate
to ant from gnu make system.

In the meantime, I'll try using the workaround you suggested.

Thanks
Nilesh

Conor MacNeill wrote:

> Nilesh,
> 
> 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
> exceptions.
> 
> 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.
> 
> Conor
> 
> 
> 
> ----- Original Message -----
> From: "Nilesh Shah" <nm...@yahoo.com>
> To: <an...@jakarta.apache.org>
> 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 -
>> 
>> Company.java - the remote interface
>> CompanyHome.java - the home interface
>> CompanyBean.java - the implementation class
>> 
>> now, the CompanyBean.java extends BeanBase.java
>> 
>> 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
>> 
>> 

Re: problem with ejbjar including base class also in the jar file

[Conor MacNeill <co...@cortexebusiness.com.au>]

Nilesh,

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
exceptions.

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.

Conor



----- Original Message -----
From: "Nilesh Shah" <nm...@yahoo.com>
To: <an...@jakarta.apache.org>
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 -
>
> Company.java - the remote interface
> CompanyHome.java - the home interface
> CompanyBean.java - the implementation class
>
> now, the CompanyBean.java extends BeanBase.java
>
> 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
>
>

Re: problem with ejbjar including base class also in the jar file

[Conor MacNeill <co...@cortexebusiness.com.au>]

----- Original Message -----
From: "Nilesh Shah" <nm...@yahoo.com>
To: <an...@jakarta.apache.org>
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 -
>
> Company.java - the remote interface
> CompanyHome.java - the home interface
> CompanyBean.java - the implementation class
>
> now, the CompanyBean.java extends BeanBase.java
>
> 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
>
>