Mailing-List: contact ant-user-help@jakarta.apache.org; run by ezmlm
From: "Joshua Davis" <jsd2000@bellatlantic.net>
To: <ant-user@jakarta.apache.org>
Subject: RE: ejbjar does not include non-bean files
Date: Fri, 22 Dec 2000 08:24:51 -0500
Message-ID: <NDBBKHNOELDNJFCHKAHIAEOECBAA.jsd2000@bellatlantic.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
In-reply-to: <46FEE020BCB4D3118C5800508B55C9283BA47A@SFOEXCHANGE>
Importance: Normal

Actually, the 'support class' issue does get a bit tricky, as the same class
may get loaded many times due to the multiple class loaders present in WLAS.
That is... unless you have disabled them.

A consultant from BEA recommended the following to me:
1. In production, disable the 'extra' Weblogic class loaders.  This will
disable the 'hot deploy' and 'servlet reloading' features, however (IMO a
good idea in production).
2. Try to ensure that each class appears *exactly once* in the classpath.
This usually means putting all 'support classes' into a separate jar, and
placing that jar in the 'system classpath' (i.e. the root-most class path in
the WLAS).

> -----Original Message-----
> From: Jeff Davies [mailto:JDavies@Ceon.com]
> Sent: Thursday, December 21, 2000 12:58 PM
> To: 'ant-user@jakarta.apache.org'
> Subject: RE: ejbjar does not include non-bean files
>
>
> Thanks for the thoughtful reply!
>
> I think that you and I are taking different approaches to the EJB issue.
> Wher I am consulting now, we have a large project that is split
> into 6 major
> components. Each component is a collection of 5+ EJBs and their supporting
> files. Each component gets compiled into a single jar. I can see
> your point
> on this. If we were compiling each EJB into its own JAR file,
> including the
> support files would be very bad indeed!
>
> Overall, I don't think this is a big issue. In my scripts now (taking the
> advice of another Ant/EJB user on this forum) I simply <exec> the jar
> command AFTER the <ejbc> task has run. This subsequent jar
> command then adds
> all of the support files to the ejb jar and everything works great!
>
> - Jeff
>
> -----Original Message-----
> From: Conor MacNeill [mailto:conor@cognet.com.au]
> Sent: Tuesday, December 19, 2000 11:17 PM
> To: ant-user@jakarta.apache.org
> Subject: Re: ejbjar does not include non-bean files
>
>
> Jeff,
>
> 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 ?
>
> Conor
>