> > Hmm - propably more consistent solution and also suppress
> that "hack".
> > There could be foundproperty (and we set it to true/false) and
> notfounddata
> > (which we would set into property if no matching node is found).
> > Message should be suppressed if either if those two is specified.
> >
> > +1 for this solution and I'm volunteer to code and
> contribute patch for
> > this.
>
> Wouldn't it just be better (and more powerful) to have
> separate tasks, or
> functions for this ?
Functions would be good, but we have to "cache" XML somewhere. Some time ago
I came with <xml> type idea but noone liked it, so I throw it away. But
maybe it could be good fit here.
<xml fromfile="foo.xml" id="foo"/>
<xmlpeek
refid="foo"
xpath="//bar"
property="..."
failonerror="true"
if="${xml::node-exists('//bat')}"
/>
We need some type for for xml:: functions parameters, don't we?
btw: we could have <xmlpeek> as an function xml::peek also.
Martin
-------------------------------------------------------
This Newsletter Sponsored by: Macrovision
For reliable Linux application installations, use the industry's leading
setup authoring tool, InstallShield X. Learn more and evaluate
today. http://clk.atdmt.com/MSI/go/ins0030000001msi/direct/01/
_______________________________________________
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
