If you write a SOAP extention let me know. I wrote a XSL Modifier to work
with the Modification Manager that does XSL transforms. Essentially it works
by interpreting the previous results as XML. XMLRequest objects serve one of
two purposes. If they are XSL stylesheets then the previous response will be
processed to create the next request. ElseIf it is just a regular XML
document, it is assumed to be the request and no modification is made.
An example tree would be
Thread Group
- Xml Test Sample (XMLa in Request )
- Modification Manager
- XSL Modifier
- Xml Test Sample (XSLb in Request)
- Xml Test Sample (XSLc in Request)
Given the above tree, the requests would look like the following:
1. Request with XMLa
- Respond with XMLresA
2. Request with XSLb(XMLresA) -- this is the resulting XML when XMLresA is
transformed by XSLb
- Respond with XMLresB
3. Request with XSLc(XMLresB)
- Server Responds with XMLresC
The only reason I never submitted it was because it was I didn't build it to
work over HTTP. JMeter has fairly tight coupleing of a request format and
its delivery mechanism. (The controller asks the sample what its sampler
is). Unfortunately, I am using a proprietary delivery mechanism so I coupled
them. However, with the thought that this might be useful to someone else, I
did minimize the impact of the coupleing into one line. I'd be happy to
share code if anybody is interested. Also may I make a side suggestion that
in future versions of JMeter we figure out a way to separate concerns with
regard to content of a request and the delivery of it.
Thanks a bunch and keep me informed of your progress with SOAP extentions.
Brian
-----Original Message-----
From: Mike Stover [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 30, 2002 9:34 AM
To: JMeter Users List
Subject: Re: SOAP and HttpUnit
You'd need to write a SOAP extension to JMeter, though that wouldn't be
hard, and
I'd be willing to do it for you if you help me out. I could write the
skeleton of what
you need, and you fill in the SOAP stuff. It's about time JMeter fully
supported
SOAP anyway.
The biggest difference between JMeter and HttpUnit is that you "program"
JMeter via
the GUI, rather than writing Java code. JMeter has a proxy server that
supports
HTTP, recording of browser activity. This proxy could easily be the basis
for a new
proxy that allowed recording of SOAP activity. Is this what you meant by
"sniff"?
JMeter also has visualizers to represent the test data. Whether or not they
meet
your needs is hard to say since you didn't specify, but I guess the answer
is, yes,
you can visualize the traffic :-)
-Mike
On 29 May 2002 at 15:14, Boris Garbuzov wrote:
> I am evaluating this product to test SOAP communication. Can somebody
> comment on its suitability for the purpose? How is it comparing to
HttpUnit?
> Can I use it to sniff and visualize the traffic? Boris.
>
>
> --
> To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>
>
--
Michael Stover
[EMAIL PROTECTED]
Yahoo IM: mstover_ya
ICQ: 152975688
--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
