Return-Path: 
 <ant-user-return-7709-apmail-jakarta-ant-user-archive=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-ant-user-archive@jakarta.apache.org
Received: (qmail 65304 invoked by uid 500); 14 May 2001 10:42:07 -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 65214 invoked from network); 14 May 2001 10:42:01 -0000
Message-ID: <004b01c0dc63$080a7530$77e4223f@cognetnt>
From: "Conor MacNeill" <conor@cortexebusiness.com.au>
To: <ant-user@jakarta.apache.org>
References: <FFEJJDBJFIPDNKKJIIOOKECJFKAA.robert@elastica.com>
Subject: Re: Don't understand ejb-jar examples.
Date: Mon, 14 May 2001 20:40:04 +1000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N

From: "Robert Nicholson" <robert@elastica.com>
> Why is the weblogic-ejb-jar.xml descriptor _excluded_?
>
> <ejbjar srcdir="${build.classes}"
>             descriptordir="${descriptor.dir}"
>             basejarname="TheEJBJar">
>       <weblogic destdir="${deploymentjars.dir}"
>                 classpath="${descriptorbuild.classpath}"/>
>       <include name="**/ejb-jar.xml"/>
>       <exclude name="**/weblogic*.xml"/>
> </ejbjar>

ejbjar processes only generic deployment descriptors. If you feed it a
weblogic deployment descriptor it will, ahh, barf.

>
> So the idea is to always build a generic jar and use a nested element
> to build a vendors server jar?

Yep. The nested element for weblogic is able to determine the weblogic
deployment descriptor based on the naming conventions for. That is why it
is not a problem to exclude the weblogic descriptor.

>
> Using this example will the weblogic descriptor get included or not?
>
>     <ejbjar srcdir="${build.classes}"
>             descriptordir="${descriptor.dir}"
>             basejarname="TheEJBJar">
>       <weblogic destdir="${deploymentjars.dir}"
>                 classpath="${descriptorbuild.classpath}"/>
>       <include name="**/ejb-jar.xml"/>
>       <exclude name="**/weblogic*.xml"/>
>     </ejbjar>
>

should be OK.

> If I'm not mistaken I'm assuming ejbjar is simply not vendor specific but
> the
> nested weblogic element knows to look for weblogic descriptors and
include
> them.

Yes..

>
> This would make sense as obviously once can then add vendor nested
> extensions
> to the ejbjar element.
>
> Here's question. How do you specify multiple srcdir's?

Currently you can't.

>
> If you look at the following Petstore rule you'll see they copy both util
> and customer classes from the same level into the buildjar directory. It
> would appear that I would
> have to do the same in order to specify a common directory that contains
> both sets
> of classes. If I was able to specify mutiple sources I wouldn't have to
do
> to this.

True.

Conor