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]
