Paul, I'm a bit of a newb....

In making the separate targets, do I do so outside of the target they
are currently in, or can they be nested?

Also, should I replace the current antWrapper with the antcall i.e., in
the same place the antWrapper steps are currently?

It also occurred to  me that using a script block (like a <groovy> step)
might be the way to go, but the groovy examples I've found have been
fairly inpenetrable....
 
Thanks
mike

> Hi Mike, try putting your Session1 exec statements into their 
> own ant target and use an antcall instead of the current antWrapper.
> The antWrapper step doesn't expand #{} within tasks like exec 
> which aren't steps at the moment. I think you are observing 
> ant's early binding "feature" which is binding the ${} 
> variables to values at the beginning of the task. You won't 
> need an antWrapper in Session2 either.
> 
> Cheers, Paul.

> > Session1:
> > <storeRegEx
> >       description="Remember registry number"
> >       text="gl[0-9]+[a-z]?"
> >       group="0"
> >       property="regNumber" 
> >       />
> > <storeProperty
> >             description="convert prop type "
> >             name="registryNumber"
> >             value="#{regNumber}" 
> >             propertyType="ant"/>
> > <antWrapper>
> > <exec executable="touch"> <arg
> > 
> value="tmp/${registry.accessLevel}.lastName.${registrantLastNa
> me.value}"
> > /></exec>
> > <exec  executable="touch"> <arg
> > value="tmp/${registry.accessLevel}.regNumber.${registryNumber}"
> > /></exec>
> > </antWrapper>
> > 
> > Session2 (separate project):
> > <antWrapper>
> > <exec executable="ls" outputproperty="lastName"><arg 
> > value="tmp/protected.lastName.*"/> </exec> <exec executable="ls" 
> > outputproperty="regNumber"><arg value="tmp/protected.regNumber.*"/> 
> > </exec> <echo message="last name is ${lastName}"/> </antWrapper>
_______________________________________________
WebTest mailing list
[email protected]
http://lists.canoo.com/mailman/listinfo/webtest

Reply via email to