How do you develop web services and how do you create WSDL? What do you include in WSDL?
This question is based on the observation that developers do not use WSDL properly. WSDL describes this service. I think that the description of the service should include everything necessary to use this service. Therefore, if I use any WS- * protocol, I must include a WS-Policy that describes this use.
I often visit the MSDN forum related to the WCF-.NET API for building web services. Almost every day, questions such as: "I have a secure Java Java service, and I need to use this service in the .net client." The first answer usually requests the WSDL of this Java web service. Unfortunately, almost every time WSDL describes only methods and messages. Security information is completely missing => that WSDL does not describe this service, because based on the information in WSDL you cannot use this service!
What is the situation in the Java world? Do you use WS policy? Do you have helper tools for creating WSDL for you if you are not prepared enough to write it? How do you exchange information about services when one team needs to consume the services provided by another team?
I also have questions from a different perspective: What problems do Java developers have when they have to consume web services created in .NET?
I feel this is a big pain in many projects where different platforms need to communicate through web services. Developers do not have a single language (which should be WSDL with politicians), and most of the time they cannot explain which WS- * functions they used because they are covered by some API. If we include the fact that only a limited set of WS- * functions is supported in the API API, we are in a complete mess. Reverse engineering a SOAP message is really time consuming.
source
share