ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dan Christopherson <>
Subject Re: ejbjar doesn't include dependent classes in jarfile?
Date Fri, 12 Jan 2001 19:08:21 GMT
On Thu, 11 Jan 2001, James Duncan Davidson wrote:

> On 1/8/01 11:20 AM, "Jason Rosenberg" <> wrote:
> > Yes,
> > 
> > It is actually recommended not to have anything other than
> > the core EJB classes included in your ejb jar file.  Dependent
> > classes should be made available in your WEBLOGIC_CLASSPATH.
> That's just good usage. Lumping everything into 'mega-jars' creates a whole
> slew of problems. Not that having applications that each contain a jndi.jar
> or a jaxp.jar is much better, but at least in that case an intelligent
> installer *might* be able to detect things and do the "right" thing.
jndi.jar or jaxp.jar is one thing, but application specific support
classes (for example, a framework supporting persistence layers in
BMP) shouldn't be in the server's classpath, but rather in an application
specific classpath. Does weblogic honor the classpath setting from

Dan Christopherson (danch) 
nVisia Technical Architect (

Opinions expressed are mine and do not neccessarily reflect any 
position or opinion of nVisia, Inc.

If you're a capitalist and you have the best goods and they're 
free, you don't have to proselytize, you just have to wait.
-Eben Moglen

View raw message