I can't quite follow the details of what you're trying to build exactly,
but it sounds like you're into the design patterns issues of your
specific thing now and have the info you need on the Ant side of the
equation to enable whatever you want.
Erik
Shackelford, John-Mason wrote:
> Erik,
>
> Now that it is all sinking in it looks like I may not be able to decouple
> the command processor task from the commands after all. If I use createXXX I
> still need to create a concrete instance that has the getters and setters I
> want Ant to populate, but I don't really want the command processor to know
> anything more about the commands than the few methods their interface
> specifies.
>
> Perhaps I need to use the DynamicConfigurator interface and then attempt to
> instanciate AbstractCommand subclasses where the subclass name matches
> nested element name. This is really what I was trying to do I just didn't
> realize that the DynamicConfigurator was the right way to do it.
>
> Thanks again for all of your time.
>
>
> John-Mason Shackelford
>
> Software Developer
> NCS Pearson - Measurement Services
> 2510 North Dodge St.
> Iowa City, IA 52245
> 319-354-9200x6214
> [EMAIL PROTECTED]
>
> ****************************************************************************
> 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: <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
>
>
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
