Web Service Publishing

Question

I have been working with web services for a long time in an academic setting, but there is one basic aspect that I do not get. There he is:

Suppose you have an application that you want to use as a web service. Thus, you create (or most likely generate) a WSDL description for it and adapt the application so that its function can be called by someone with access to this WSDL description. You now have a fully functional web service. But how do you really let people know where to find him and what he represents?

I know the UDDI initiative, but imho, which has already begun to fail. It doesn’t even make much sense to ALWAYS publish their web services in one place, and the large companies supporting it seem to understand this. So what are your options? As you can tell people, “Hey, look at this nice web service API I made for you. Here are the WSDL files.” Are you just linking to the WSDL descriptions on your web page?

Answer 1

Write some documents and examples for him and publish them along with links to the service on your website. That’s all you need.

Here is an example of a good documentation website:

http://code.google.com/apis/maps/documentation/webservices/index.html