Return-Path: Delivered-To: apmail-jakarta-ant-dev-archive@apache.org Received: (qmail 17854 invoked from network); 6 Jan 2002 14:00:08 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 6 Jan 2002 14:00:08 -0000 Received: (qmail 11413 invoked by uid 97); 6 Jan 2002 14:00:06 -0000 Delivered-To: qmlist-jakarta-archive-ant-dev@jakarta.apache.org Received: (qmail 11395 invoked by uid 97); 6 Jan 2002 14:00:06 -0000 Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Ant Developers List" Reply-To: "Ant Developers List" Delivered-To: mailing list ant-dev@jakarta.apache.org Received: (qmail 11371 invoked from network); 6 Jan 2002 14:00:05 -0000 Message-ID: <001e01c196b9$cd166e40$0100a8c0@jose> From: "Jose Alberto Fernandez" To: "Ant Developers List" References: <3C3701A3.40606@cortexebusiness.com.au> <025101c196b1$21467d10$6401a8c0@darden.virginia.edu> Subject: Re: IntrospectionHelper request Date: Sun, 6 Jan 2002 13:55:28 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N From: "Erik Hatcher" > Without delving deep into IntrospectionHelper, I'd like to bounce off = an > idea and see how its taken. Create an interface (named DynaTask? - = I've > been following commons-dev DynaBean discussions so can't think of = anything > more original) that has a method (setDynaAttribute?) with the = signature > setDynaAttribute(String name, String value). If no setter is found in = the > current process of finding one, if the class implements the "dynamic" > interface then the interfaces method is called. >=20 This comment may be good or bad for the acceptance of what you are = proposing (given my record of success of the list ;-) ). I am all for something = like this. I would go a step further and also require your dynamic interface to = manage elements (as well as attributes). So the interface would be something = like: interface DynamicConfigurator { void setDynamicAttribute(String name, String value); Object createDynamicElement(String name); } This will allow writing tasks that have their own dynamic subset of = valid elements, for example would not have to be modified every time a new EJB container is supported, but instead the new plug-in will be = declared in some registry and the task will use createDynamicElement() to search = for the correct plug-in element to instantiate. The same is applicable to things like , , etc.=20 And it would finally allow to define a real useful