ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shackelford, John-Mason" <>
Subject RE: DynamicConfigurator passing fully qualified class name
Date Wed, 21 Aug 2002 21:23:09 GMT

>I'm confused by what you are asking here.  FQN of what exactly?  The 
>class that is implementing the DynamicConfigurator interface (you have 
> that already)?

Sorry to be unclear.

All I was suggesting is that IntrospectionHelper.createElement could check
to see of the tag is already associated with a class via <typedef> or
<taskdef> and, if so, pass in a FQN to
DynamicConfigurator.createDynamicElement(String name) since that will reduce

On second thought, perhaps it would be better to have a signature
DynamicConfigurator.createDynamicElement(ProjectComponent pc)and pass in an
instantiated ProjectComponent when we can do so instead of calling the
signature that takes a String. 

I suggest this because it seems to me that instantiate a Task or DataType in
createDynamicElement(String name) will be done so frequently that it should
be "pulled up" into IntrospectionHelper.

John-Mason Shackelford

Software Developer
NCS Pearson - Measurement Services
2510 North Dodge St.
Iowa City, IA 52245

This email may contain confidential material. 
If you were not an intended recipient, 
Please notify the sender and delete all copies. 
We may monitor email to and from our network. 

To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message