Return-Path: Delivered-To: apmail-jakarta-ant-user-archive@jakarta.apache.org Received: (qmail 19458 invoked by uid 500); 20 Jun 2001 17:15:51 -0000 Mailing-List: contact ant-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Reply-To: ant-user@jakarta.apache.org Delivered-To: mailing list ant-user@jakarta.apache.org Received: (qmail 19261 invoked from network); 20 Jun 2001 17:15:48 -0000 Message-ID: <0AACAA2B6D5CD51197E000B0D049B0C51BF86F@bstreet.marrakech.com> From: "M.A.Dunphy" To: "Ant-User (E-mail)" Subject: ejbjar: What goes into the generic jar before call weblogic ejbc compiler tool? Date: Wed, 20 Jun 2001 18:13:32 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C0F9AC.5537B820" X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C0F9AC.5537B820 Content-Type: text/plain; charset="iso-8859-1" > ** Sharing a primary key class between entity beans. ** > > I have a problem with the ejbjar task in Ant. > > I have a number of entity beans whose primary key > classes are basically identicle. In fact they all > just subclass a simple base class called Key. I'd > prefer not to bother subclassing Key, but use it > directly as the primary key class of the various > entity beans. > > In the ejb-jar.xml file I supply the fully qualified > name of the Key class. However when I try to build > the project I am hitting a problem. Ant seems to be > attempting to grab the Key.class file to include in > the bean's generic jar file. This is causing problems > because the Key.class file is in a jar, not built as > part of the project. Ant cannot find the Key.class > file and so cannot build the generic jar; it doesn't > get as far as invoking weblogic.ejbc. > > I can achieve the required results by hand. When make > the generic jar by hand, I don't need to add the > Key.class file to the jar. The other bean classes do > go in (the remote and home interfaces, etc.). The xml > descriptor goes in too, as normal. It references a > class that is not in the generic jar file (ie. the > Key class). > > The weblogic.ejbc utility runs fine against this > generic jar file, as long as the Key is on the class > path. The weblogic.ejbc utility needs to be able to > load the Key class, so that it can compile its container > classes (the same as it needs the String class), but > it doesn't need to include the Key.class file in the > final jar. > > Can I stop the ejbjar task from trying to include the > class files for the classes mentioned in by deployment > descriptor? > > ------_=_NextPart_001_01C0F9AC.5537B820 Content-Type: text/html; charset="iso-8859-1" ejbjar: What goes into the generic jar before call weblogic ejbc compiler tool?

** Sharing a primary key class between entity beans. **

I have a problem with the ejbjar task in Ant.

I have a number of entity beans whose primary key
classes are basically identicle. In fact they all
just subclass a simple base class called Key. I'd
prefer not to bother subclassing Key, but use it
directly as the primary key class of the various
entity beans.

In the ejb-jar.xml file I supply the fully qualified
name of the Key class. However when I try to build
the project I am hitting a problem. Ant seems to be
attempting to grab the Key.class file to include in
the bean's generic jar file. This is causing problems
because the Key.class file is in a jar, not built as
part of the project. Ant cannot find the Key.class
file and so cannot build the generic jar; it doesn't
get as far as invoking weblogic.ejbc.

I can achieve the required results by hand. When make
the generic jar by hand, I don't need to add the
Key.class file to the jar. The other bean classes do
go in (the remote and home interfaces, etc.). The xml
descriptor goes in too, as normal. It references a
class that is not in the generic jar file (ie. the
Key class).

The weblogic.ejbc utility runs fine against this
generic jar file, as long as the Key is on the class
path. The weblogic.ejbc utility needs to be able to
load the Key class, so that it can compile its container
classes (the same as it needs the String class), but
it doesn't need to include the Key.class file in the
final jar.

Can I stop the ejbjar task from trying to include the
class files for the classes mentioned in by deployment
descriptor?


------_=_NextPart_001_01C0F9AC.5537B820--