ELECTIVE COURSE - V – 2- WEB SERVICES
Unit I
Introduction: What are web services? SOAP WSDL UDDI-Why Web Services are important? – The
evolution of web applications Not just another distributed computing platform – Web services and
enterprises.
Unit II
XML Fundamentals: The Lingua Franca of web services- XML Documents-XML namespaces Explicit and
Default namespaces, Inheriting namespaces, And not inheriting namespaces, Attributes and namespaces
-XML Schema XML schema and namespaces, A first schema, Implementing XML schema types, The any
Element, Inheritance, Substitution groups, Global and local type declarations, Managing Schemas,
Schemas and instance documents, XML schema best practices
Unit III
Overview of SOAP – HTTP – XML-RPC – SOAP: Protocol – Message Structure – Intermediaries – Actors –
Design Patterns And Faults – SOAP With Attachments.
Unit IV
UDDI at a glance- The UDDI Business registry- UDDI under the covers – Accessing UDDI- How UDDI is
playing out
Unit V
Conversations: Overview – Web Services – Web services Conversation Language – WSCL Interface
components – The Bar scenario conversations – Relationship between WSCL and WSDL
Text Book(s)
1. Sandeep Chatterjee, James Webber, “Developing Enterprise Web Services”, Pearson Education, 2004.
2. Frank. P. Coyle, XML, Web Services And The Data Revolution, Pearson Education, 2002. 3. Ramesh
Nagappan , Robert Skoczylas and Rima Patel Sriganesh, “ Developing Java Web Services”, Wiley
Publishing Inc., 2004. 4. McGovern, et al., “Java Web Services Architecture”, Morgan Kaufmann
Publishers,2005.
Unit I
Introduction: What are web services? SOAP WSDL UDDI-Why Web Services are important? – The
evolution of web applications Not just another distributed computing platform – Web services and
enterprises.
Introduction: What are web services?
Web services are application components
Web services communicate using open protocols
Web services are self-contained and self-describing
Web services can be discovered using UDDI
Web services can be used by other applications
XML is the basis for Web services
SOAP WSDL UDDI
The basic Web services platform is XML + HTTP.
XML provides a language which can be used between different platforms and programming
languages and still express complex messages and functions.
The HTTP protocol is the most used Internet protocol.
Web services platform elements:
SOAP (Simple Object Access Protocol)
UDDI (Universal Description, Discovery and Integration)
WSDL (Web Services Description Language)
Why Web Services are important?
The evolution of web applications Not just another distributed computing platform
Web services and enterprises.
Unit II
XML Fundamentals: The Lingua Franca of web services- XML Documents-XML namespaces Explicit and
Default namespaces, Inheriting namespaces, And not inheriting namespaces, Attributes and namespaces
-XML Schema XML schema and namespaces, A first schema, Implementing XML schema types, The any
Element, Inheritance, Substitution groups, Global and local type declarations, Managing Schemas,
Schemas and instance documents, XML schema best practices
XML namespaces Explicit and Default namespaces, Inheriting namespaces, And not inheriting
namespaces
What Is an XML Namespace?
An XML namespace is a collection of names that can be used as element or attribute names in an
XML document. The namespace qualifies element names uniquely on the Web in order to avoid
conflicts between elements with the same name. The namespace is identified by some Uniform
Resource Identifier (URI), either a Uniform Resource Locator (URL), or a Uniform Resource
Name (URN), but it doesn't matter what, if anything, it points to. URIs are used simply because
they are globally unique across the Internet.
Namespaces can be declared either explicitly or by default. With an explicit declaration, you
define a shorthand, or prefix, to substitute for the full name of the namespace. You use this prefix
to qualify elements belonging to that namespace. Explicit declarations are useful when a node
contains elements from different namespaces. A default declaration declares a namespace to be
used for all elements within its scope, and a prefix is not used.
How Do I Declare an Explicit Namespace?
The following explicit declaration declares bk and money to be shorthand for the full names of
their respective namespaces. The xmlns attribute is an XML keyword for a namespace
declaration.
<BOOKS>
<bk:BOOK xmlns:bk="urn:example.domain.com/BookInfo"
xmlns:money="urn:Finance:Money">
<bk:TITLE>Creepy Crawlies</bk:TITLE>
<bk:PRICE money:currency="US Dollar">22.95</bk:PRICE>
</bk:BOOK>
</BOOKS>
How Do I Declare a Default Namespace?
A namespace declared without a prefix becomes the default namespace for the document. All
elements and attributes in the document that do not have a prefix will then belong to the default
namespace. The following example declares that the <BOOK> element and all elements and
attributes within it (<TITLE>, <PRICE>, currency) are from the namespace
urn:example.microsoft.com/BookInfo.
XML
<BOOK xmlns="urn:example.microsoft.com/BookInfo">
<TITLE>Creepy Crawlies</TITLE>
<PRICE currency="US Dollar">22.95</PRICE>
</BOOK>
<BOOK xmlns="http://example.domain.com/BookInfo">
<TITLE>Creepy Crawlies</TITLE>
<PRICE currency="US Dollar">22.95</PRICE>
</BOOK>
