What does it mean for WSDL to be "correct"?

What does it mean for WSDL to be "correct"?

What does it mean for WSDL to be "correct"?

    Requires Free Membership to View

    Login

    When you register, you'll begin receiving targeted emails from my team of award-winning writers. Our goal is to keep you informed on recent service-oriented architecture (SOA) and SOA-related topics such as integration, governance, Web services, Cloud and more.

    Hannah Smalltree, Editorial Director

    By submitting your registration information to SearchSOA.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchSOA.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

A more appropriate term would be "valid". A WSDL file is an XML document. It's structure is defined by an XML Schema (http://schemas.xmlsoap.org/wsdl/). If a WSDL document does not conform to its schema, it's invalid. Then again, a WSDL document could be valid, but if it doesn't accurately describe a Web service, it's not much use. A WSDL document describes:

- what a services does (what operations it performs and the format of the messages that much be exchanged when performing those operations)
- how to communicate with it (what protocols it supports and how to encode the data)
- where it lives (it's access point)

If the information in the WSDL document doesn't match the specifics of the Web service, it's not correct.

This was first published in May 2002

Back to top