sebb wrote:
I think that has already have been done via a property -
jmeter.httpsampler - but it could be turned into a GUI option.
Yes, that setting controls what class the HTTPSamplerFactory will
instantiate.
But by changing it to HTTPSampler2, and trying to use the HTTP Proxy,
you get an exception
from the HTTPSampler :
2007/03/17 18:15:58 ERROR - jmeter.protocol.http.proxy.Proxy:
java.lang.NullPointerException
at
org.apache.jmeter.protocol.http.sampler.HTTPSampler2.setupConnection(HTTPSampler2.java:333)
at
org.apache.jmeter.protocol.http.sampler.HTTPSampler2.sample(HTTPSampler2.java:569)
at
org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample(HTTPSamplerBase.java:722)
at org.apache.jmeter.protocol.http.proxy.Proxy.run(Proxy.java:124)
This is caused by the fact that the threadStartet() on the HTTPSampler
is not being called by the Proxy.
One also has to change the code so that the correct GUI class for the
HTTPSampler2 is sent from the Proxy.
So the Proxy as it is today, does not support the HTTPSampler2.
All seem sensible ideas to me.
The proxy uses the generated sampler to talk to the server, so it may
be a bit tricky to set some of the options. Or it may just be a
question of changing the options after the sampler has been used.
Thanks for the comments.
I've added bugzilla enhancement 41876 for this, and will supply a patch
for it in a few minutes.
And I will probably add more functionality and patches for the same
issue in the near future.
If anyone cares to have a look at the patches, or test it, it would be
very useful.
Regards
Alf
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
