I'm working on an application that talks to a client's web application using SOAP. So the client has given use the url to send SOAP messages to. Anyhow, as part of my validation code, I'll like to check if I can send messages to the client using the URL. The URL we have can be incorrect, point to the wrong place or some other problem.
In my validation can I just check if I can obtain a SocketConnection to the machine? For example:
Don't check - but fail gracefully. It should be simple enough to provide the client with an incorrect URL to find out what exception is thrown by your particular SOAP stack (example) - then add code to deal with that exception gracefully. With HTTP you connect to send a request; what request are you going to send? If that URL is a SOAP endpoint you better send a SOAP request; if you have to send a SOAP request you might as well try to get some work done. [ March 02, 2008: Message edited by: Peer Reynders ]
Lasagna is spaghetti flvored cake. Just like this tiny ad: