Return-Path: 
 <ant-user-return-9485-apmail-jakarta-ant-user-archive=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-ant-user-archive@jakarta.apache.org
Received: (qmail 63489 invoked by uid 500); 27 Jun 2001 01:38:22 -0000
Mailing-List: contact ant-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Post: <mailto:ant-user@jakarta.apache.org>
List-Help: <mailto:ant-user-help@jakarta.apache.org>
List-Unsubscribe: <mailto:ant-user-unsubscribe@jakarta.apache.org>
List-Subscribe: <mailto:ant-user-subscribe@jakarta.apache.org>
Reply-To: ant-user@jakarta.apache.org
Delivered-To: mailing list ant-user@jakarta.apache.org
Received: (qmail 63475 invoked from network); 27 Jun 2001 01:38:18 -0000
Sender: mikew@byrd.int.cortexebusiness.com.au
To: ant-user@jakarta.apache.org
Subject: Re: ejbjar changes and questions
References: <002901c0fe4c$14cc8050$d7c8223f@cognetnt>
From: Mike Williams <mikew@cortexebusiness.com.au>
Date: 27 Jun 2001 11:37:38 +1000
In-Reply-To: <002901c0fe4c$14cc8050$d7c8223f@cognetnt>
Message-ID: <m3pubqg0t9.fsf@byrd.int.cortexebusiness.com.au>
Lines: 50
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.0.103
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N

  >>> On Wed, 27 Jun 2001 00:20:35 +1000,
  >>> "Conor" == "Conor MacNeill" <conor@cortexebusiness.com.au> wrote:

  Conor> One thing I have in mind is to try and get the support code
  Conor> included automatically by determining class dependencies rather
  Conor> than through the <support> element which doesn't work well when
  Conor> processing multiple descriptors. 

That would be Very Nice Indeed (TM).

  Conor> Another thing would be to combine descriptors into a single output
  Conor> jar. I want to retain the incremental approach of bean per jar
  Conor> while avoiding the duplication of support code.

Perhaps ejbjar could provide support for dependencies between jar-files
using the Extension Mechanism Architecture? (as described in section
8.1.1.2 of the J2EE-1.3 PFD3 spec).  That way, you wouldn't have to merge
EJBs into a single jar-file ... you'd just have all your EJB jars depend on
a common support-code jar.

Here's how it might work ...

- Ant target looks something like this:

        <ejbjar descriptordir="ejb/dd" srcdir="build/ejb/classes"
                supportjar="support.jar">
            <weblogic destdir="build/ejb/jars" ... />
            <include name="*-ejb-jar.xml"/>
            <exclude name="*-weblogic-ejb-jar.xml"/>
        </ejbjar>

- ejbjar processes all the DDs in "ejb/dd"

- The result, in "build/ejb/jars", is

    BeanA.jar
    BeanB.jar
    ...
    support.jar

- The META-INF/MANIFEST.MF files for "BeanX.jar" contains

    "Class-Path: support.jar"

- "support.jar" contains all the dependent classes

Does this seem useful?

-- 
Mike