Browse Prior Art Database

A system for propagating client side code to invoke a self-describing service at invocation time.

IP.com Disclosure Number: IPCOM000010755D
Original Publication Date: 2003-Jan-16
Included in the Prior Art Database: 2003-Jan-16
Document File: 2 page(s) / 79K

Publishing Venue

IBM

Abstract

A mechanism is disclosed to provide a means of allowing a client of a web service to acquire the necessary executable code to implement a defined WSDL binding at runtime, using WSDL extensibility elements. The mechanism defines a means of defining the location of the code that implements the binding in WSDL, such that a web service client may download this code and execute it to parse the rest of the WSDL binding section to configure the connection behaviour of the client.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 50% of the total text.

Page 1 of 2

  A system for propagating client side code to invoke a self-describing service at invocation time.

Web Services currently describe themselves using the Web Service Description Language (WSDL). WSDL consists of three parts, a portType that describes the abstract application interface, a binding that describes how that interface is used for a given transport protocol, and the port that is the actual connection details for a portType and binding pair. The portType is an XML Schema definition, and can therefore be parsed and interpreted in a standard and well-defined way. However, the binding, although described in a standard syntax using an extensible schema definition, has no standard for actually describing the functional semantics. In otherwords, for a binding to be used, it must be parsed and interpreted by a piece of code that has been explicitly written for that binding - the binding requires a matching code pair. Therefore, for a client to use the service, they must have access to that code ahead of time before they can interpret the WSDL.

   Disclosed is a system for allowing a client to acquire that code at invocation time, potentially remotely, dispensing with the need to ensure the necessary client side code has been deployed in order to use any given service.

   The WSDL binding specifies a name for that binding, the portType it is associated with, and then concrete grammar for how the messages described in the portType are carried for this binding. The combination of binding name and portType make a unique entity. WSDL uses extensibility elements to describe the gra...