Jose Alberto Fernandez wrote:
Why should ANT become a multilingual routing processor
for XML? I think it is a fantastic project but it is not the ANT
project.
I do not see anyone asking XSLT engines to do this kind of thing. The XSLT XML processing is for the XSLT, not for doing all for all
XML dialects. Same for ANT.
If you are interested in this kind of thing, point your browser at http://1060.org and d/l a build of NetKernel -preferably 2.1 when it ships shortly. This is definitely a generic XML processor engine which does plenty much magic, like (in v2.1) autobinding a database select to an XML document for later xformation.
I am debating moving all my statically/dynamically generated content to this system, though need to get a bit better at xpointer first.
Returning to Ant, we are a build tool, not a generic workflow engine -even if a lot of the XML workflow/PI stuff at the w3c shows ant experience. The problem of getting project to ship roughly what was asked for, on or before the date promised, is hard enough without introducing more complexity
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
