I am just thinking that less tasks is better. If we can add <echoxml> functionality into existing <echo> tasks there will less documentation and code to maintain.
- Alexey. On 5/24/05, Matt Benson <[EMAIL PROTECTED]> wrote: > > --- "Alexey N. Solofnenko" <[EMAIL PROTECTED]> > wrote: > > Do you mean, that the current <echo> task cannot be > > made to accept > > XMLFragment? > > It could, but for easiest coding, the XMLFragment > would then be represented by a discrete nested > element: > > <echo file="foo.xml"> > <xml> > <foo blah="bar"> > <foochild /> > <foochild /> > <foochild /> > </foo> > </xml> > </echo> > > Alternatively, <echo> could itself be made to > implement DynamicElement/NS and would basically need > to clone code from XMLFragment. Either way you would > probably need to enforce mutual exclusion of (nested > text/message attribute) or nested XML. So no, I don't > suppose there is any reason you couldn't do it this > way. > > -Matt > > > > - Alexey. > > > > Matt Benson wrote: > > > > >--- Alexey Solofnenko <[EMAIL PROTECTED]> wrote: > > > > > > > > >>Why not to add this functionality into normal > > >><echo>? > > >> > > >> > > > > > >I suppose if you wanted to use entities, <echo> > > >already can do this (clumsily). This task (OUCH > > >actually doesn't compile b/c I forgot a file) was > > >exceedingly easy and enforces well-formedness of > > the > > >nested XML due to its being parsed as XML. > > > > > >-Matt > > > > > > > > >>- Alexey. > > -- Alexey N. Solofnenko trelony at gmail.com <http://gmail.com> home: http://trelony.cjb.net/ Pleasant Hill, CA (GMT-8 hours usually)
