You could, however, implement a placeholder object that stores a Properties
object, and a collection of itself, and implements the DynamicConfigurator
interface. For attributes it receives, it could add them to the properties
collection, and for elements nested within, it could add it to the
collection.
This would give you a "DOM" of sorts, which would represent the XML tree.
DynamicConfigurator is an Ant 1.5 addition.
Erik
----- Original Message -----
From: "Steve Loughran" <[EMAIL PROTECTED]>
To: "Ant Developers List" <[EMAIL PROTECTED]>
Sent: Tuesday, June 25, 2002 7:35 PM
Subject: Re: A Type object that accepts anything as a nested value
> ----- Original Message -----
> From: "Kevin Grey" <[EMAIL PROTECTED]>
> To: "Ant Developers List" <[EMAIL PROTECTED]>
> Sent: Tuesday, June 25, 2002 2:55 PM
> Subject: A Type object that accepts anything as a nested value
>
>
> >
> > Heya,
> >
> > Is it possible to create a Type in ANT that can be handed
all
> > nested elements as a DOM tree (or equivalent)? That is, rather than
doing
> > addTYPE() for each nested element, you'd be able to just receive
> everything
> > in one function call and interpret it on your own...
>
> no. not in ant 1.x; its an artifact of the way it parses everything iself.
> So, no, you cant have arbitrary XML inside a task.
>
>
> --
> 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]>
