Skip to main content

By clicking Submit, you agree to the developerWorks terms of use.

The first time you sign into developerWorks, a profile is created for you. Select information in your profile (name, country/region, and company) is displayed to the public and will accompany any content you post. You may update your IBM account at any time.

All information submitted is secure.

  • Close [x]

The first time you sign in to developerWorks, a profile is created for you, so you need to choose a display name. Your display name accompanies the content you post on developerworks.

Please choose a display name between 3-31 characters. Your display name must be unique in the developerWorks community and should not be your email address for privacy reasons.

By clicking Submit, you agree to the developerWorks terms of use.

All information submitted is secure.

  • Close [x]

Understanding web services, Part 2: Web Services Description Language (WSDL)

Sharing web services

Photo of Nicholas Chase
Nicholas Chase has been involved in Web site development for companies such as Lucent Technologies, Sun Microsystems, Oracle, and the Tampa Bay Buccaneers. Nick has been a high school physics teacher, a low-level radioactive waste facility manager, an online science fiction magazine editor, a multimedia engineer, an Oracle instructor, and the Chief Technology Officer of an interactive communications company. He is the author of several books, including XML Primer Plus (Sams).

Summary:  The current emphasis on Service-Oriented Architectures (SOA) has put the spotlight on web services, but it's easy to get lost in all the information being bandied about. This series gives you the straight story on all of the major web service specifications, starting with Simple Object Access Protocol (SOAP) and working down to WS Business Process Execution Language (WS-BPEL). In this second installment, you'll learn about Web Services Definition Language, as the Daily Moon Classified Department uses WSDL to describe their own web service in such a way that others can easily create clients to access it from any programming language or platform.

View more content in this series

Date:  07 Jul 2006
Level:  Intermediate PDF:  A4 and Letter (153 KB | 58 pages)Get Adobe® Reader®

Activity:  35817 views
Comments:  

Summary

In Part 1 of this series, the Classifieds Department of the Daily Moon newspaper learned how to use SOAP web services to connect with the newspaper's Content Management System. In this tutorial, the staff learned to use Web Services Description Language (WSDL) to describe their own services so that others could use them. The tutorial covered the basics of XML schema, along with the structure of a WSDL file so that it can be built by hand. It also discussed the differences between the various styles and encodings available. The tutorial also explained how to use the Java2WSDL and WSDL2Java tools that come with Apache Axis2 to automatically generate WSDL from Java files, and vice versa.

Part 3 of this series will look at building web service registries using UDDI.

7 of 10 | Previous | Next

Comments



static.content.url=http://www.ibm.com/developerworks/js/artrating/
SITE_ID=1
Zone=SOA and Web services
ArticleID=145033
TutorialTitle=Understanding web services, Part 2: Web Services Description Language (WSDL)
publish-date=07072006
author1-email=ibmquestions@nicholaschase.com
author1-email-cc=