The major part it to allow tasks to take over the parsing of the build.xml
document possibly
by allowing them to load their own DocumentHandlers. This requires the
changes I
outlined and could be done before namespace support (making sure there is no
name collisions).
Erik Hatcher wrote:
> ----- Original Message -----
> From: "Richard Emberson" <emberson@phc.net>
> > TWO - Task wrapping application which uses xml to specify its behavior:
> >
> > I have an application that uses xml to specify its behavior much
> > like Tomcat or Ant (element tag name to class mappings plus attributes).
> >
> > What I'd like to do is simply embed as child
> > elements of the wrapper task's element the application's xml.
>
> Wouldn't this be resolved in the future by supporting XML namespaces and
> having a specific namespace for Ant-recognized elements, and use your own
> inside tasks where Ant would pass-through non-Ant namespaced elements?
>
> --
> To unsubscribe, e-mail: <mailto:ant-dev-unsubscribe@jakarta.apache.org>
> For additional commands, e-mail: <mailto:ant-dev-help@jakarta.apache.org>
--
To unsubscribe, e-mail: <mailto:ant-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-dev-help@jakarta.apache.org>
|