Groups | Blog | Home
all groups > dotnet web services > august 2006 >

dotnet web services : SOAP exception


Yossi
8/21/2006 1:00:45 PM
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?

John Saunders
8/21/2006 7:21:01 PM
[quoted text, click to view]

SOAP Faults are always returned in a 500 error.

John

Arindrajit Biswas
8/22/2006 1:26:02 AM
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]
AddThis Social Bookmark Button