Viewing in browser does not generate proper SOAP messages.
It would be a good idea to test your WebService using a small test
application. That's easy and you can customise/verify all condition.
[quoted text, click to view] "John Saunders" wrote:
> "Yossi" <josephceasar@firstfi.com> wrote in message
> news:u5kYcQVxGHA.4968@TK2MSFTNGP03.phx.gbl...
> > VS2005
> >
> > I have a web service that runs just fine. On the server side I always
> > return a string that either indicates failure or returns the requested
> > data. I want to raise SOAPExceptions instead of returning a string with
> > the value set to "method failed".
> >
> > So I modified my code, but I am unable to test it. Right now, from
> > VS2005, I am right clicking on my web service and then clicking on
> > "Display in browser". I then click on my web service, type in the
> > parameters and then click on the "Invoke" button. I get the correct
> > results (i.e. XML data) when the operation succeeds, but when I raise the
> > SOAP exception, I get an http error 500 with the standard "page not found"
> > message. How come I don't get XML data with the SOAP exception?
>
> SOAP Faults are always returned in a 500 error.
>
> John
>
>