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 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]> wrote: > > > > 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 sampler, or use > > an > > > external file. > > > > > > were you trying to record a webservice test plan using JMeter proxy? due > > to > > > the nature of webservices and apache soap, it's probably not going to > > work. > > > Or is the problem you're having using jmeter + soap ws + jmeter proxy > > port > > > settings? > > > > > > > > > peter > > > > > > > > > On 10/17/05, Michael Riedling <[EMAIL PROTECTED]> wrote: > > > > > >>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" encoding="UTF-8"?><env:Envelope xmlns:env="http://schema..."; > > >> > > >>btw. if I copy the Soap Message in a SOAP Request Sampler by hand, it > > >>works. > > >> > > >> > > >> > > >>sebb schrieb: > > >> > > >>>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 eliminating the JMeter proxy - > > >>>i.e. run the test plan directly - and report back. > > >>> > > >>>S. > > >>> > > >>> > > >>>On 17/10/05, Michael Riedling <[EMAIL PROTECTED]> wrote: > > >>> > > >>> > > >>>>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 Manager entries - these can be changed if necessary. > > >>>>> > > >>>>>S. > > >>>>>On 14/10/05, Michael Riedling <[EMAIL PROTECTED]> wrote: > > >>>>> > > >>>>> > > >>>>> > > >>>>>>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 code: 415 > > >>>>>>HTTP response message: Unsupported Media Type > > >>>>>> > > >>>>>>HTTP response headers: > > >>>>>>HTTP/1.1 415 Unsupported Media Type > > >>>>>>Server: Apache-Coyote/1.1 > > >>>>>>X-Powered-By: Servlet 2.4; JBoss-4.0.2 (build: CVSTag=JBoss_4_0_2 > > >>>>>>date=200505022023)/Tomcat-5.5 > > >>>>>>Content-Type: text/xml > > >>>>>>Date: Fri, 14 Oct 2005 12:43:57 GMT > > >>>>>> > > >>>>>> > > >>>>>>When i use Etherreal (Network Protocol Analyzer) to analyze the > > >> > > >>packets, > > >> > > >>>>>>i found out that JMeter changes the content-type in the Request > > Header > > >>>>> > > >>>>>>from "text/xml" to "application/x-www-form-urlencoded" which is then > > >> > > >>not > > >> > > >>>>>>supported by the HTTP Server. > > >>>>>> > > >>>>>>Any ideas, explanations, workarounds or solutions? > > >>>>>> > > >>>>>>Thx in advance, > > >>>>>> > > >>>>>>- Michael > > >>>>>> > > >>>>>> > > >>>>>> > > >>>>>> > > >>>>>> > > > > >>>>>>--------------------------------------------------------------------- > > >>>>>>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] > > >>>>> > > >>>>> > > >>>>> > > >>>> > > >>>>-- > > >>>>STZ-IDA an der Hochschule Karlsruhe > > >>>>email [EMAIL PROTECTED] > > >>>>internet http://stz-ida.de > > >>>>fon ++49 - 721 - 9 20 33 00 Moltkestrasse 30 > > >>>>fax ++49 - 721 - 9 68 32 88 D-76133 Karlsruhe/Germany > > >>>> > > >>>>--------------------------------------------------------------------- > > >>>>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] > > >>> > > >>> > > >>> > > >> > > >>-- > > >>STZ-IDA an der Hochschule Karlsruhe > > >>email [EMAIL PROTECTED] > > >>internet http://stz-ida.de > > >>fon ++49 - 721 - 9 20 33 00 Moltkestrasse 30 > > >>fax ++49 - 721 - 9 68 32 88 D-76133 Karlsruhe/Germany > > >> > > >>--------------------------------------------------------------------- > > >>To unsubscribe, e-mail: [EMAIL PROTECTED] > > >>For additional commands, e-mail: [EMAIL PROTECTED] > > >> > > >> > > >> > > > > > > > > > > -- > > STZ-IDA an der Hochschule Karlsruhe > > email [EMAIL PROTECTED] > > internet http://stz-ida.de > > fon ++49 - 721 - 9 20 33 00 Moltkestrasse 30 > > fax ++49 - 721 - 9 68 32 88 D-76133 Karlsruhe/Germany > > > > --------------------------------------------------------------------- > > 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]
