On 29/10/2007, Woody Aichner <[EMAIL PROTECTED]> wrote:
> I just looked the HtmlUnit and the dependent jars. This could create a
> problem:
>
> jaxen-1.1.1.jar                            not used by Jmeter
> commons-collections-3.2.jar       same as Jmeter
> commons-lang-2.3.jar                 same as Jmeter
> commons-httpclient-3.0.1.jar       Jmeter uses commons-httpclient-3.1.jar

If HtmlUnit does not work with 3.1, then that is definitely a problem
- and not just for JMeter ;-)

> comons-codec-1.3.jar                 same as Jmeter
> js-1.6R5.jar                                 Jmeter us js_rhino1_6R5 (not
> sure this is the same thing or not)

Probably same.

> xercesImpl-2.6.2.jar                    Jmeter uses xercesImpl.jar

JMeter is using xalan 2.7.0. It used to use an earlier version; no
code changes were needed when updating so it's unlikely to be a
problem for HtmlUnit either.

> xmlParserAPIs-2.6.2.jar             not used by Jmeter

Seems to be part of xerces.

> nekohtml-0.9.5.jar                      not used by Jmeter
> commons-logging-1.1.jar            same as Jmeter
> commons-io-1.3.1.jar                 same as Jmeter

I don't think there is a problem here.

> ----- Original Message -----
> From: "sebb" <[EMAIL PROTECTED]>
> To: "JMeter Users List" <[email protected]>
> Sent: Sunday, October 28, 2007 9:37 PM
> Subject: Re: Re[2]: Interest for a combination of JMeter with HtmlUnit /
> WebTest for AJAX load testing?
>
>
> >I think that adding extra processing to JMeter to deal with processing
> > client-side Javascript is counter-productive in general.
> >
> > Although it would be convenient for some tests, it's a waste to keep
> > reprocessing the Javascript in order to decide what URL to sample next
> > - or to keep scanning the HTML to find out how to submit a particular
> > form. Using the JMeter Proxy to record the session allows the work to
> > be done by the browser when creating the test plan; it does not have
> > to be repeated for every test.
> >
> > However, if anyone wants to develop an HtmlUnit sampler it could be
> > done as an optional plugin.
> >
> > The HtmlUnit API seems fairly straight-forward - it could be called
> > from a BeanShell sampler, at least as proof of concept.
> >
> > But I suspect that designing a GUI for it would not be trivial.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to