Dale Anson wrote:
I'm not up on the code, but I like the concept, and I like the idea of
retrofitting existing tasks to use a generic resource rather than
methods for each specific type. My original question was about having
the XmlProperty task read from a property as well as a file, I've always
wanted similar functionality in the "get" task -- it only writes the
response to a file, when on occassion it would be much handier to write
it to a property so subsequent tasks could act directly on the response.
Dale
the moment i commit my updated http antlib, <http:get> will save the
response and/or http status code to properties.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
