> From: iggchamp > I didn't see anything about the wsdl in the video though.
Glad the stuff on our site helps! You saw in the video how easy it is to create a web service from Visual Studio. The beauty of it is that you never need to see the WSDL. Many of our colleagues spend time manually building SOAP documents in BASIC or tweaking WSDL when there are tools to do this automatically and transparently. When you point your browser to the service you get a web page with a summary of the service and a list of functions. Your URL would look something like this: http://localhost:8181/OurServices/WS1.asmx There is a link on that page to "Service Description". Click on that and you're presented with the full WSDL for your service. The URL looks like this: http://localhost:8181/OurServices/WS1.asmx?WSDL Give your associates either link, or email them the WSDL. They should be able to access the service from any language or framework. Seriously, this part of it takes about 10 minutes. Plug in the code that Symeon provided for UO.NET and you have a complete solution in less than 1/2 hour. The only thing that might complicate this is if you really need to accept XML and return XML, not as part of the envelope but as the payload, or if you need to deal with arrays of objects. These things are still easy in a full .NET solution but if the client isn't .NET then all parties need to be more generic about the data types. Research will lead you to solutions. HTH T ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
