On Fri, 30 Nov 2001 20:43, Stefan Bodewig wrote: > > TWO - Task wrapping application which uses xml to specify its > > behavior: > > > > The simplest way to do this is to allow such task to use its own > > DocumentHandler (maybe the wrapper task can have a DocumentHandler > > derived from the ProjectHelper.AbstractHandler if it were public) > > and install it when the task's element tag is recognized, > > elementStart and removed at endElement. Oh yea, the application has > > its own introspector. > > Sounds like a lot of work inside Ant to avoid specifying and > maintaining separate configuration files 8-)
But it also allows us to do ContainerTasks in task-land rather than requiring all sorts of support from container. > How would you identify tasks that want to attach their own > DocumentHandlers? The corresponding class implements a marker > interface? Have a look at the myrmidon proposal ;) > > THREE - Dynamically set the tag-2-class in Introspector. > > This is something we really need (and want) to experiment with. Allow > different implementations of a given interface to be used as nested > elements. A start has been proposed by Conor about a week ago, search > for "[IDEA] Polymorphic types" in the archives. Alternatively look at the myrmidon proposal that has had this implemented for close to a year ;) -- Cheers, Pete -------------------------------------------------- Where ignorance is bliss, 'tis folly to be wise. -------------------------------------------------- -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
