Web Service Inspection

WEB SERVICE INSPECTION:

While UDDI is the best- -known mechanism for service known mechanism for service discovery, it is neither the only mechanism nor always the discovery, it is neither the only mechanism nor always the best tool for the job. In many cases, the complexity and best tool for the job. In many cases, the complexity and scope of UDDI is overkill if all that is needed is a simple scope of UDDI is overkill if all that is needed is a simple pointer to a WSDL document or a services pointer to a WSDL document or a services URL endpoint. Recognizing this, IBM and Microsoft got URL endpoint. Recognizing this, IBM and Microsoft got together and worked out a proposal for a new Web Service together and worked out a proposal for a new Web Service Inspection Language that can be used to create a simple Inspection Language that can be used to create a simple An example WS An example WS- -Inspection document is illustrated in Inspection document is illustrated in Examples. It contains a reference to a single service 38. It contains a reference to a single service (Hello World) with two descriptions (Hello World) with two descriptions— —one WSDL one WSDL- -based based description and one UDDI description and one UDDI- -based description. index of service descriptions at a given network location.

<?xml version="1.0"?><?xml version="1.0"?> <inspection <inspection

xmlns xmlns="http://schemas.xmlsoap.org/ws/2001/10/inspection/" ="http://schemas.xmlsoap.org/ws/2001/10/inspection/"

xmlns:uddi xmlns:uddi="http://schemas.xmlsoap.org/ws/2001/10/inspection/uddi/"> ="http://schemas.xmlsoap.org/ws/2001/10/inspection/uddi/">

<service><service>

<abstract>The Hello World Service</abstract><abstract>The Hello World Service</abstract> <description <description

referencedNamespace referencedNamespace="http:// ="http://schemas.xmlsoap.org/wsdl schemas.xmlsoap.org/wsdl/" /"

location="http:// location="http://example.com/helloworld.wsdl example.com/helloworld.wsdl"/> "/>

<description <description referencedNamespace referencedNamespace=" ="urn:uddi urn:uddi- - org:api org:api"> ">

<<uddi:serviceDescription uddi:serviceDescription

location="http:// location="http://www.example.com/uddi/inquiryapi www.example.com/uddi/inquiryapi"> ">

<<uddi:serviceKey uddi:serviceKey>>

4FA28580 4FA28580- -5C39 5C39- -11D5 11D5- -9FCF 9FCF- -BB3200333F79 BB3200333F79

</ </uddi:serviceKey uddi:serviceKey>>

</ </uddi:serviceDescription uddi:serviceDescription>> </description></description>

</service></service> <link <link referencedNamespace

referencedNamespace="http://schemas.xmlsoap.org/ws/2001/10/inspection/"

="http://schemas.xmlsoap.org/ws/2001/10/inspection/"

location="http:// location="http://example.com/moreservices.wsil example.com/moreservices.wsil"/> "/>

</inspection>

WEB SERVICE INSPECTION WEB SERVICE INSPECTION SYNTAX:

The syntax of a WS The syntax of a WS- -Inspection document is simple. The root inspection Inspection document is simple. The root inspection element contains a collection of element contains a collection of

·                    abstract

·                    link

·                    service elements.

The abstract element provides for simple documentation throughout the WS the WS- - Inspection document. The link element allows the inspection document to link to otherexternal inspection documents or even other discovery mechanism.The Programming Web Services with SOAP Programming Web Services with SOAP service element represents service element represents a web service being offered by the publisher of the inspection a web service being offered by the publisher of the inspection document. The service element itself is a collection of abstract and description elements. You can describe a service in several ways.