Return-Path: 
 <ant-dev-return-14397-apmail-jakarta-ant-dev-archive=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-ant-dev-archive@jakarta.apache.org
Received: (qmail 53340 invoked by uid 500); 5 Jun 2001 11:26:57 -0000
Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ant-dev@jakarta.apache.org
list-help: <mailto:ant-dev-help@jakarta.apache.org>
list-unsubscribe: <mailto:ant-dev-unsubscribe@jakarta.apache.org>
list-post: <mailto:ant-dev@jakarta.apache.org>
Delivered-To: mailing list ant-dev@jakarta.apache.org
Received: (qmail 52299 invoked from network); 5 Jun 2001 11:26:54 -0000
From: "Jose Alberto Fernandez" <j_a_fernandez@yahoo.com>
To: <ant-dev@jakarta.apache.org>
Subject: RE: DataType interface?
Date: Tue, 5 Jun 2001 12:28:19 +0100
Message-ID: <000f01c0edb2$9f3f47e0$da76883e@viquity.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
In-Reply-To: <005301c0edaf$f79dfd80$d5ef3c3f@cognetnt>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N

> From: Conor MacNeill [mailto:conor@cortexebusiness.com.au]
>
>
>
> How about this instead
>
> <foo>
>    <myimprovedfileset ...>
> </foo>
>
> When this is encountered and there is no createMyImprovedFileset,
> introspection looks for an interface that is supported by both the
> myimprovedfileset element and an nestedlementcreator of foo.
>
> I haven't thought through the details here in terms of how the
> introspection can perform that piece of magic but it seems
> doable and has
> the advantage that the user's intent is explicit - no funky search for
> potential matching types.
>

This assumes that every taks can only have one attribute/element of each
particular interface. Which is not true today. For example several tasks
allow for several Path definitions. I do not think we want the buildfiles to
guess things around.

I think we are confusing the typename with the task attribute name. Several
tasks use the  name of the type as the name of the attribute but they are
different things. The name of the element inside foo is that of its
attribute, not that of the type of the attribute.

Jose Alberto