Hi, I don't think so. The problem I had was with loading the WSDL--which isn't actually that critical. You don't need to load the WSDL as you can manually enter the server you want to connect to and send the SOAP envelope to. I believe you need to make sure the first line of your SOAP request states that it's an xml document.
Here's an example (modified to remove confidential information, but the structure is correct.) of a SOAP request that works for me: <?xml version="1.0" encoding="utf-8"?> <soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/";> <soap-env:Body> <ns1:TEST xmlns:ns1="http://serverHost/services/";></ns1:TEST> </soap-env:Body> </soap-env:Envelope> It won't work for you exactly as is because you won't have the same service; however it is a valid SOAP request and maybe that will help... (note the first line--I think it's important. Rob > -----Original Message----- > From: Stephanie Fuller [mailto:[EMAIL PROTECTED] > Sent: Wednesday, May 10, 2006 11:12 AM > To: JMeter Users List > Subject: RE: WSDL Loading Revisted (not processing WSDL correctly?) > > Is it possible that my WSDL & Soap problem is related to this one??? > > I am using JMeter 2.1.1. I defined a SOAP/XML Request sampler and typed > in the soap envelope as given to me by the programmer. JMeter fails, > saying 'SOAP version mismatch or invalid SOAP message'. Do I need to > convert my soap envelope to .net? The programmer says it is gsoap format, > but it still fails... How do I go about changing the envelope format to > .net? Can you recommend a resource to explain the .net format? > > In the same test plan I have a Web Service SOAP) Request sampler. It > successfully loads my WSDL (same one the previous soap envelope came from) > and populates the Web Methods menu, and when I select a method and click > on Configure, the next 4 fields are populated (Server Name/IP, Port > Number, Path & SOAPAction). However, that sampler also fails, with no > Request or Response data in the results tree. In this case I have one > unknown - I had to put the WSDL file at my webapp port (8080), but the > application that it should talk to is on port 8000. So, I manually > changed the port number, but still it fails. > > Which listener is recommended? What can I do to get these to work, or at > least understand why they aren't working? > Thanks very much for any insight you can offer. > > Stephanie R. Fuller > Spearhead Innovations Inc. > > ________________________________ > > From: Peter Lin [mailto:[EMAIL PROTECTED] > Sent: Wed 5/10/2006 11:37 AM > To: JMeter Users List > Subject: Re: WSDL Loading Revisted (not processing WSDL correctly?) > > > > glad you were able to get around it. please go ahead and open an > enhancement bugzilla. out of curiousity, which Webservice toolkit are you > using? > > > I know there's been changes in the soap webservice wsdl world, so it's > likely compatability with newer tools are going to break badly. > > peter > > > On 5/10/06, Rob Johnson <[EMAIL PROTECTED]> wrote: > > > > Thanks Peter. I was successful in manually entering the various > > parameters and getting a SOAP request to work; however, the WSDL part > > wouldn't import and populate the parameters as you suspected. > > > > I'll attempt to simplify the issues I'm having and submit a bugzilla > > enhancement to see if it can help clarify what might be useful to > > implement. > > > > Of course, it would be nice to have a general implementation of WSDL > > importing for testing--even though it is a black art. :-) > > > > Thanks much, > > Rob > > > > > -----Original Message----- > > > From: Peter Lin [mailto:[EMAIL PROTECTED] > > > Sent: Tuesday, May 09, 2006 8:02 PM > > > To: JMeter Users List > > > Subject: Re: WSDL Loading Revisted (not processing WSDL correctly?) > > > > > > the WSDL tools is very primitive. Since i wrote it, I can say it's > > really > > > a > > > dumb parser and expects the WSDL to follow .NET 1.0 or 1.1 format. Any > > > other > > > format will likely fail miserably. So far i've test it with .NET 1.0 > > & > > > 1.1, > > > Axis, JWSDP and gSoap generated WSDL. > > > > > > Even if the WSDL is valid, how soap action is declared and used varies > > > significantly. Feel free to open an enhancement bugzilla and if I have > > > time > > > I'll take a look. Your other options is to manually enter those > > values. > > > the > > > configure tool is meant to be a convienance. WSDL definition is a bit > > of a > > > black art and rather complex. It's been a while since I looked a the > > spec. > > > > > > hope that answers your questions > > > > > > peter > > > > > > > > > On 5/9/06, Rob Johnson <[EMAIL PROTECTED]> wrote: > > > > > > > > I've been fighting with the Web Services testing all day using > > jMeter > > > > 2.1.1. I've pretty much determined that jMeter is not processing > > the > > > > WSDL properly. The WSDL is valid and in use in other applications. > > > > > > > > > > > > > > > > When I plug in the URL for the WSDL and click "load WSDL", and then > > pick > > > > a method and select "CONFIGURE", it does not correctly populate the > > > > URL/port/SOAPAction from the WSDL. Instead, it populates those > > fields > > > > with the location of the WSDL, not the location of the service. > > > > > > > > > > > > > > > > Has anyone else come across this? Does anyone else successfully > > test > > > > Web Services with jMeter? > > > > > > > > > > > > > > > > Thanks much in advance, > > > > > > > > Rob > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > 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]
