How to handle invalid web service namespace error

[Ajay Choudhary]

Hi,

If the client tries to access a web service with invalid namespace, it gets
a SOAP exception as invalid SOAPAction.
The invalid namespace will happen because the proxies on the client side
were generated before the namespace on the server side was updated.
I would like to handle this myself and throw a SOAP exception with more
information in it.
How can I do that?

Thanks,
Ajay

Serve Code - The namespace is updated from "1111" to "2222".
[WebService(Name space=http://NoServerWithThi sName/Services/SayHello/2222)]

public class SayHello : System.Web.Serv ices.WebService

{

[WebMethod]

public string HelloWorld()

{

return "Hello World from "+Environment.U serName;

}

}

Client Proxy Code - Notice the "1111"

[System.Web.Serv ices.WebService BindingAttribut e(Name="SayHell oSoap",
Namespace=http://NoServerWithThi sName/Services/SayHello/1111)]

public class SayHello : System.Web.Serv ices.Protocols. SoapHttpClientP rotocol
{

....

}

Client Code -

try

{

SayHello s = new SayHello();

MessageBox.Show (s.HelloWorld() );

}

catch(Exception ex)

{

MessageBox.Show (ex.Message);

}

[Chad Z. Hower aka Kudzu]

"Ajay Choudhary" <aj***********@ hotmail.com> wrote in
news:Oq******** ******@TK2MSFTN GP15.phx.gbl:

If the client tries to access a web service with invalid namespace, it
gets a SOAP exception as invalid SOAPAction.
The invalid namespace will happen because the proxies on the client side
were generated before the namespace on the server side was updated.
I would like to handle this myself and throw a SOAP exception with more
information in it.

Where do you want to handle it, client side or server side?
--
Chad Z. Hower (a.k.a. Kudzu) - http://www.hower.org/Kudzu/
"Programmin g is an art form that fights back"

Blog: http://blogs.atozed.com/kudzu

[Ajay Choudhary]

On the server side I would like to throw my own exception to clients with my
information in it.

"Chad Z. Hower aka Kudzu" <cp**@hower.org > wrote in message
news:Xn******** *********@127.0 .0.1...

"Ajay Choudhary" <aj***********@ hotmail.com> wrote in
news:Oq******** ******@TK2MSFTN GP15.phx.gbl:

If the client tries to access a web service with invalid namespace, it
gets a SOAP exception as invalid SOAPAction.
The invalid namespace will happen because the proxies on the client side
were generated before the namespace on the server side was updated.
I would like to handle this myself and throw a SOAP exception with more
information in it.

Where do you want to handle it, client side or server side?
--
Chad Z. Hower (a.k.a. Kudzu) - http://www.hower.org/Kudzu/
"Programmin g is an art form that fights back"

Blog: http://blogs.atozed.com/kudzu

[Chad Z. Hower aka Kudzu]

"Ajay Choudhary" <aj***********@ hotmail.com> wrote in
news:ex******** ******@tk2msftn gp13.phx.gbl:

On the server side I would like to throw my own exception to clients
with my information in it.

Im not sure of anyway offhand. But the webservices classes (both serve and
client) are very flexible. You'll need to dig around a bit and see if you can
hook in at the lower level.

If you cant - you could set up a redirect using a HTTP handler or ASHX, and
then preparse. If its ok, issue a HTTP redirect to send them to the real
webservice, else return the error.
--
Chad Z. Hower (a.k.a. Kudzu) - http://www.hower.org/Kudzu/
"Programmin g is an art form that fights back"

Blog: http://blogs.atozed.com/kudzu