ahh ok. if you're hitting IIS, you will need to make sure the soapAction
value in the webservice (SOAP) sampler is correct. if not, ASPX/ASMX will
return an error.

peter


On 11/14/05, Richard Gaywood <[EMAIL PROTECTED]> wrote:
>
> On 11/14/05, Richard Gaywood <[EMAIL PROTECTED]> wrote:
> >
> >
> >
> > On 11/14/05, Peter Lin <[EMAIL PROTECTED]> wrote:
> > >
> > > can you send a sample test plan to me directly and I'll take a look
> > > tonight.
> > > Just in case, make sure there isn't a blank line before <?xml ...>
> > > there's a
> > > know bug with crimson that causes a xml parse error.
> > >
> >
> > I'll try and get you one later. One thing I did just notice is that the
> > JMX file has HTML escaping in the HTTPSampler.xml_data entry
> corresponding
> > to my SOAP request, i.e.
> >
> >
> > <stringProp name="HTTPSamper.xml_data">&lt;?xml version=&quot;1.0&quot;
> > encoding=&quot;utf-8&quot;?&gt;
> > &lt;soap:Envelope
> > xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
> > xmlns:xsd=&quot;http://www.w3.org/2001/XMLSchema&quot;
> > xmlns:soap=&quot;http://schemas.xmlsoap.org/soap/envelope/&quot;&gt;
> > &lt;soap:Body&gt;
> >
> >
> > (etc)
>
>
>
>
> Oops, sent that too soon. What I meant to write was, is there perhaps a
> problem with JMeter not undoing the escaping before putting the SOAP on
> the
> wire to the server? To thicken the plot further, if I cut and paste the
> XML
> out of my WebService(SOAP) Request element and int a SOAP/XML-RPC Request
> element instead, then the error message changes to "Unable to handle
> request
> without a valid action parameter. Please supply a valid soap action."
> which
> looks to me like it's getting further along.
>
>

Reply via email to