Hi Michael,
are you sure that you don't have an other problem. I've made a small
test and once set with <setproxy>, the proxy system properties are still
available in build files called from the main one what seems logical.
Btw, you've said that you run (or want to run) your webtest with a proxy
to record it and use it to perform load testing with the grinder. Does
it means that it reuses the sessions created by the webtests? Can you
give more details about the process?
Marc.
Michael Habbert wrote:
> Hi Marc,
>
> actually we do have a lot of theses:
>
> <!--
> ==========================================================================================
> -->
> <!-- == LAUNCH
> CREATECONTRACTOR
>
> -->
> <!--
> ==========================================================================================
> -->
> <import file="imports/createContractor.xml" />
> <target name="launchCreatecontractor">
> <ant antfile="${webtest.launch.xml}">
> <property file="properties/createcontractor.properties" />
> </ant>
> </target>
>
> and a main target in the same build-file:
>
> <target name="usecases1" description="run usecase-tests part 1 - first
> do the main creation.">
> <antcall target="launchCreatecontractor" />
> [...]
> </target>
>
> So if I define a proxy in this build.xml inside the imported xml-files
> with the single target-definitions there isn't any knowledge of the
> proxy any more ;-/
> System.property is gone! (with or without a new jvm ;-)
>
> So forget about the starting jvm ;-). In fact: I was not able to
> configure the proxy in the main build.xml file to convince the webtest
> to take the configured proxy.
>
> Michael
>
>
> Marc Guillemot wrote:
>> You didn't tell that you start a new JVM. Why do you do that? Can't you
>> pass the proxy properties there?
>>
>> Marc.
>>
>> Michael Habbert wrote:
>>> Hi Marc,
>>>
>>> yes, I traced the problem down last week and the only explanation was:
>>>
>>> If I set the proxy by ant-task: <setproxy> in the upper build.xml, they
>>> are not available in the lower build.xml and therefore the webtests are
>>> not aware of the proxy.
>>>
>>> As far as I know the ant-task(proxy) adds the property to the
>>> system.properties useable for this jvm. A newly started jvm starts with
>>> the clean collection of system.properties, nothing about the proxy.
>>>
>>> Michael
> [...]
>
_______________________________________________
WebTest mailing list
[email protected]
http://lists.canoo.com/mailman/listinfo/webtest
