Newletter Sign Up
Posts on the
Design Decomposition Blog
Iridium Satellite Collision in Space
You might have seen the recent news reports about the collision between U.S. and Russian communication satellites. The U.S. satellite was one of the Iridium satellites. What wasn’t reported and you probably don’t know is that an object database management system (ODBMS) is an important part of the Iridium system. Even though ODBMSs are a [...]
February 13, 2009
(The Acronym) SOA is (Perhaps) Dead (at Some Companies); Long Live Services
I am now also posting on the Cutter Blog. My initial posting is (The Acronym) SOA is (Perhaps) Dead (at Some Companies); Long Live Services. It is a response to Anne Thomas Manes’ SOA is Dead; Long Live Services on her blog at the Burton Group.
January 9, 2009
Atomicity
The typical definition of an atomic task or process is one that cannot be decomposed further. This is vague and subject to interpretation. The Decomposition Matrix on this site uses a specific definition: A task (for business process diagrams) or a process (for data flow diagrams) is atomic if every input relates to every output [...]
December 3, 2008
Well-Formed Business Process Diagrams
My last posting referenced the criteria for a well-formed business process diagram mentioned in Business Process Driven SOA using BPMN and BPEL by Matjaz B. Juric and Kapil Pant. I am going to expand on their criteria to create a more comprehensive definition of a well-formed business process diagram. To start, here are three criteria from [...]
November 18, 2008
Recent Business Process Modeling Books
I recently received two new books on business process modeling. Both books looked interesting because they had great titles. As it turns out, one book is great and the other not so good. The not so good book is Business Process Driven SOA using BPMN and BPEL by Matjaz B. Juric and Kapil Pant. There are [...]
October 9, 2008
The Design Decomposition Blog
is written by Doug Barry.

Web Services Description Language (WSDL) is a format for describing a Web Services interface. It is a way to describe services and how they should be bound to specific network addresses. WSDL has three parts:

Definitions are generally expressed in XML and include both data type definitions and message definitions that use the data type definitions. These definitions are usually based upon some agreed upon XML vocabulary. This agreement could be within an organization or between organizations. Vocabularies within an organization could be designed specifically for that organization. They may or may not be based on some industry-wide vocabulary. If data type and message definitions need to be used between organizations, then most likely an industry-wide vocabulary will be used. For more on XML vocabularies, click here

XML, however, is not necessary required for definitions. The OMG Interface Definition Language (IDL), for example, could be used instead of XML. If a different definitional format were used, senders and receivers would need to agree on the format as well as the vocabulary. Nevertheless, over time, XML-based vocabularies and messages are likely to dominate. XML Namespaces (new window) are used to ensure uniqueness of the XML element names in the definitions, operations, and service bindings.

Operations describe actions for the messages supported by a Web service. There are four types of operations:

Operations are grouped into port types. Port types define a set of operations supported by the Web service.

Service bindings connect port types to a port. A port is defined by associating a network address with a port type. A collection of ports defines a service. This binding is commonly created using SOAP (new window), but other forms may be used. These other forms could include CORBA Internet Inter-ORB Protocol (IIOP), DCOM, .NET, Java Message Service (JMS), or WebSphere MQ to name a few.

The following figure shows the relationship of the basic parts of WSDL:

Basic parts of WSDL

Also see XML vocabularies (new window).

Organization: W3C

More information: WSDL page on the W3C website (new window)

Related content for: Web Services Description Language (WSDL)

More on the general topic: Service

Read more free articles on this site

There are nearly 400 pages of articles on this site with over 130 pages on Web services and service-oriented architecture.

Search this site for more articles

Custom Search

Browse this site for more articles

Click on the topics below to browse the articles on this site. You can see more detail by clicking on the arrows. This highlights the location of the current article: Web Services Description Language (WSDL).

Related recent articles from Google News

Mobile Collaboration Tools Uptake Fueled by Smartphone Surge
CMSWire
SMS, XML and WSDL. The push engine supports TCP/IP, CTP and CMS to Microsoft Outlook and other email clients. It registers and provisions devices and ...

18 Mar 2010 at 12:08pm
Leveraging Your Host Systems with SOA Web Services
SYS-CON Media (press release)
There is a Web Service Description Language (WSDL) file associated with each Web service message type that tells the application what to do with the content ...

23 Feb 2010 at 8:37am
Why Web Services Failed at SOA (and Why REST May Fail Too!)
SYS-CON Media (press release)
Worse, the WSDL included that option and WSA did not discouraged the practice! I may think it was because there were tools supporting this and the idea was ...

10 Mar 2010 at 7:17am
Why Intermediaries Matter in SOA
SYS-CON Media (press release)
Steve describes this bad practice as follows: This anti-principle is all about where people just get a WSDL and consume it directly without any proxy or ...
and more »
16 Mar 2010 at 5:48am
5 Things to Consider when Integrating your Content Management System and Portal
CMSWire
The appropriate Web Service client must be generated from the service WSDL via JAX-WS or Axis, or some other tool. This would be consumed from Portlet ...

9 Mar 2010 at 9:27am
More related news on: "Web services" WSDL

Related books at Amazon.com

WSDL 100 Success Secrets Essentials of Understanding and Applying Web Services Description Language - THE XML based protocol for information exchange in decentralized and distributed environments
WSDL 100 Success Secrets Essentials of Understanding and Applying Web Services Description Language - THE XML based protocol for information exchange in decentralized and distributed environments
by Kevin Allen
Average Customer Review: 1 star based on 1 review.
Customer Review: There is nothing of value in this book. It's all filler. Each chapter begins with the reminder that WSDL means Web Services Description Language. Here's a typical sentence (page 31): When you try to at look (sic) at the Internet, you will be amused to know for yourself (sic) how useful, how modernized, how high-tech, and how beneficia...
More related books: Search Amazon.com for Web services