-----Original Message----- From: webt...@lists.canoo.com [mailto:webt...@lists.canoo.com]On Behalf Of Dierk König Sent: Dienstag, 7. Mai 2002 14:18 To: webt...@lists.canoo.com Subject: [Webtest] config element change poll

Hiall,

thinking through the current config element, I spotted a possiblity of change.

The current element is used like this:

<config host="${host}" port="${port}" protocol="${protocol}" basepath="${basepath}" summary="true" verbose="true" saveresponse="true" resultpath="${resultpath}" resultfile="${resultfile}" haltonfailure="true" showhtmlparseroutput="true" />

How about setting the attributes automatically where the attribute name is identical to an ANT parameter name?

example: attribute "host" would be set automatically to the current value of "${host}".

The above block would collapse to:

<config summary="true" verbose="true" saveresponse="true" haltonfailure="true" showhtmlparseroutput="true" />

or to: <parameter name="summary" value="true"/> <parameter name="verbose" value="true"/> <parameter name="saveresponse" value="true"/> <parameter name="haltonfailure" value="true"/> <parameter name="showhtmlparseroutput" value="true"/> ... <config/>

Individual usages of config could more easily override specific parameters. <config resultpath="some/other/weird/path" />

Would this change be in conflict with any of the current usages of the config element or parameter usages out there?

cheers Mittie