ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Robert Watkins <robert.watk...@qsipayments.com>
Subject RE: [DISC] details of task library concept
Date Thu, 24 May 2001 04:31:32 GMT
> Every EJB is defines with its HOME and Object interface in the XML
> descriptor every resource with its type is defined there. All Homes
> corresponding to other web or EJB applications used by this one are
> described in the XML descriptor. The ear file is suppose to 
> contain all the
> jars that the EJB requires. And all that (i think) is 
> mentioned in the XML
> descriptor.

Yes, the EAR is meant to hold everything. And the EJB Jar (and the WARs, and
the RARs) are meant to have Class-Path entries to the jar files, relative to
their location in the EAR.

Yes, there are dependencies listed in the XML. For example, an ejb-ref would
declare the home and remote interfaces. However, all that states is that
whatever is mapped to the relative JNDI entry must conform to those
interfaces, and that those interfaces are on the class-path. It doesn't say
anything about where they live. These are dependencies, but they are not
class-path dependencies. Amongst other things, versioning is not addressed
in this manner (but they are via the manifest file)

Hmm... one way of viewing it is that the deployment descriptors say what the
EJB is dependent on, but says nothing about where to look for those
dependencies.

> And the container uses that information to locate things. Now 
> if those are
> not dependencies I do not what.

The container isn't supposed to hunt through all the JARs. If an EJB needs a
class, it's meant to look (in this order) in: the JAR file in the EJB,
followed by the Class-Path entries in the manifest file.

Robert.

-- 
     "Duct tape is like the Force: it has a light side, a dark side,
                   and it holds the universe together"
  Robert Watkins     robertdw@bigpond.net.au     robertw@qsipayments.com

Mime
View raw message