That´s it. I tried to record Soap Requests from a Java Client with the
JMeter Proxy. But the Record Controller detected it as a Http Request.
Peter Lin schrieb:
I'm not sure I understand the problem. the soap webservice sampler was
designed so that users can past the soap message in the
unfortunately, that's a limitation of jmeter's proxy. It really only expects
request parameters. Microsoft's webservice toolkit has a proxy that is
designed to record SOAP calls, you might want to try using that to record
the soap calls.
peter lin
On 10/18/05, Michael Riedling [EMAIL PROTECTED]
However, it might be possible to add some checks in the JMeter Proxy
code to see if the request was a SOAP request and generate the
appropriate Sampler.
Dunno how difficult that would be - I've never used SOAP.
S.
On 18/10/05, Peter Lin [EMAIL PROTECTED] wrote:
unfortunately, that's a
I suppose it's possible, too bad I have no clue how the jmeter proxy
recorder works.
the soap message is usually in the request body. I suppose we could add a
simple option for the proxy recorder so that users can check it. when it's
checked, it just grabs the entire request body as a soap
Would one ever want to record SOAP as well as HTTP in the same session?
S.
On 18/10/05, Peter Lin [EMAIL PROTECTED] wrote:
I suppose it's possible, too bad I have no clue how the jmeter proxy
recorder works.
the soap message is usually in the request body. I suppose we could add a
simple
normally, the answer would be no, but that depends on the webservice
toolkit.
AFAIK, Sun, IBM and MS webservice toolkits don't explicitly say do not
mix. from my experience the last 3 years, webservice calls are between
systems, so it's generally the important information is in the httpheader
and
I´ve tried that already.
Although the content-type in the header manager shows me text/xml, The
outgoing request from JMeter Proxy is with content-type
application/x-www-form-urlencoded... :/
see here: http://www.home.hs-karlsruhe.de/~rimi0024/dl/screen.jpg
sebb schrieb:
Check the Header
That appears to show that the JMeter Proxy has detected the
content-type as text/html, but the SOAP Sampler is sending
application/x-www-form-urlencoded.
So the problem does not seem to be anything to do with the JMeter
Proxy, but with the SOAP Sampler.
Perhaps you can double-check this by
Yes ur right, of course. Same problem appears without JMeter Proxy.
It´s the Soap Sampler.
The Thing is that the JMeterproxy doesn´t recognize my Web Service
request as Web Service Request, it records the Requests as HTTP Requests
with Parameter ?xml version and Value
1.0
That's because the JMeter Proxy was written for HTTP Requests, and
does not take account of the newer SOAP Sampler.
Perhaps raise a Bugzilla enhancement request?
If you could also raise a bug report with examples of what does and
does not work, that would be helpful.
S.
On 17/10/05, Michael
Hello,
I have the following problem:
All is working fine with my Java Clients (which communicates SOAP
Messages with a Web service on an remote Server) and the JMeter Proxy in
stand alone tests, but when i use JMeter as proxy for my Java Clients
the following error occurs:
HTTP response
11 matches
Mail list logo
