Craeg K Strong wrote:
Shackelford, John-Mason wrote:
Craeg,
It would be great if there could be some new Ant resource of some kind -- perhaps a new datatype -- that represented a chunk of parsed XML.
<snip/>
By having the xmldatatype tag I could move the deployment definition out of
the build file and into a configuration file. My build script would then
look some thing like:
<xmldatatype file="my.xml" class="org.apache.leftfield.DeploySet" elementname="deployset" id="my.deployset"/>
<deployset deploysetref="my.deployset" key="${deployment.box}" propertyprefix="deploy.box"/>
<echo> Preparing to deploy to: ftphost = ${deploy.box.ftphost} ftpuser = ${deploy.box.ftpuser} </echo>
Would something like this help?
John-Mason Shackelford
Our requirements are quite different, but I bet there is a design for an <xmldatatype> that could satisfy both requirements. If the data type represented a DOM, then perhaps it could also provide some kind of XPath support. That way you could grab the value of a node out of it:
<?xml version="1.0"?> ...
<deployset>foo</deployset> ...
using an XPath expression. Is that what you were thinking? That would be very useful IMHO.
Look at proposal/embed, it already does all of this, and *much* more :-)
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
