Brent Bain wrote:
I've tried the task that Peter Reilly attached to one of the emails about a
month ago for an XPath iterator but I can't seem to get it to work with the
current ant-contrib tasks.
I tested it with the latest ant-contrib - 1.0b1, you may have an older
version in your path.
Also, it
Without looking at the XML in detail you could certainly use xmltask,
and call ant targets for each xml node representing (say) a machine.
To call a stop script for each machine:
or similar (haven't tried / tested the above, btw.)
I can advise further offline if need be.
Jacob Kjome wrote:
Or use something like XMLTask...
http://www.oopsconsultancy.com/software/xmltask/index.html
Jake
Quoting [EMAIL PROTECTED]:
> This is what I have been doing to arrange my data in XML files. Its a bit
> crooked way of organizing data but
> it is read very easily and readily available in properti
This is what I have been doing to arrange my data in XML files. Its a bit
crooked way of organizing data but
it is read very easily and readily available in properties.
e.g. in your case I would change the format of the XML file to something
like this.
Machine1
Machine2
Hello:
I am trying to figure out how to handle the data being passed to me by my IT
department. They finally agreed to send me an xml document (see snippet
below) and that should have made my life much simpler.
Maybe I should describe what I'm trying to do:
I am attempting to stop multiple res
