WO2002001356A1 - Technique de conversion de types facilitant le teleappel de services - Google Patents

Technique de conversion de types facilitant le teleappel de services Download PDF

Info

Publication number
WO2002001356A1
WO2002001356A1 PCT/US2001/019007 US0119007W WO0201356A1 WO 2002001356 A1 WO2002001356 A1 WO 2002001356A1 US 0119007 W US0119007 W US 0119007W WO 0201356 A1 WO0201356 A1 WO 0201356A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
tag
type
conversion
xml
Prior art date
Application number
PCT/US2001/019007
Other languages
English (en)
Other versions
WO2002001356A9 (fr
Inventor
Christopher S. Taylor
Timothy Gordon Kimmet
Original Assignee
Aladdin Knowledge Systems, Ltd.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Aladdin Knowledge Systems, Ltd. filed Critical Aladdin Knowledge Systems, Ltd.
Priority to EP01946318A priority Critical patent/EP1305710A4/fr
Publication of WO2002001356A1 publication Critical patent/WO2002001356A1/fr
Publication of WO2002001356A9 publication Critical patent/WO2002001356A9/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/54—Interprogram communication
    • G06F9/547—Remote procedure calls [RPC]; Web services

Definitions

  • the present invention relates to distributed computing, in particular client/server communication and server/server communication.
  • the SOAP (Simple Object Access Protocol) protocol is XML-based and enables a client's request to be communicated over HTTP, across the Internet and through firewalls.
  • XML documents are used for encoding of the invocation requests and responses.
  • a method request is represented as an XML element with additional elements for parameters.
  • the SOAP protocol considerably simplifies remote method invocation. Nevertheless, SOAP makes no provision for type conversion, i.e., mapping between XML and data types usable by the method being invoked and, in the reverse direction, between data types and XML.
  • Two techniques are known.
  • One technique encodes data types through "introspection,” i.e., programmatically inspecting an object, walking through its member variables, and turning each into XML.
  • the present invention provides a messaging framework including a flexible type conversion facility for use in remote method invocation via the Internet.
  • the framework receives a message, it decodes the message, converts any parameters into objects, locates the appropriate message handler, invokes the requested method on that handler, and communicates a return value (or exception) via a response message.
  • the return value or exception
  • Dynamic type conversion of parameters into objects is performed using a tag library system. In the tag library system, special user-defined modules (called "type factories”) are handed XML elements for conversion into objects.
  • the factory is not required to extract all of the content during a conversion, but can pass the raw XML content to the constructed object for later use.
  • Figure 1 is a block diagram of one computing environment using the present messaging framework
  • Figure 2 is a diagram showing the organization of a tag library used to perform conversion between XML and code objects
  • Figure 3 is a conceptual diagram illustrating conversion from XML
  • Figure 4 is a block diagram of another computing environment using the present messaging framework.
  • FIG. 5 is a block diagram showing in greater detail various components of the present messaging framework.
  • FIG. 1 a block diagram is shown of one computing environment using the present messaging framework, referred to as the "Ivory” messaging framework.
  • the messaging framework (configuration 101) is shown as residing within a container 103.
  • An example of one such container is a "servlet,” i.e. , an extension similar to a Java applet except that it runs on the server instead of the client.
  • Servlets are described in greater detail in Taylor and Kimmet, Core Java Web Server, Prentice Hall, 1999, incorporated herein by reference.
  • the messaging framework consists of a collection of components which, when initialized to an operational state, form a configuration of the messaging framework. These components include, as shown in Figure 1, a request message decoder 105, tag conversion routines 107, an invoker module 109, type conversion routines 111, and a response message encoder 113.
  • the messaging framework interacts with various user-define modules 115 that perform the desired services.
  • the message request decoder 105 receives an XML request message, e.g., a SOAP message, decodes the message, and for different tags of the XML message, passes the XML for the tag to a tag conversion routine 107.
  • Tag conversion routines 107 receive as input the XML for a tag and produce as output corresponding code objects (e.g., Java objects).
  • the message request decoder 105 makes these objects available to the invoker module 109 along with a corresponding command.
  • the invoker module 109 receives the command and invokes a corresponding user defined module 115 to perform the actual requested work.
  • the invoker modules 109 receives command results, in the form of objects, from the user defined module 115 and returns these results to the response message encoder 105.
  • the response message encoder 113 receives the result objects and for different ones of the objects, passes the object to a corresponding type conversion routine 111.
  • Type conversion routmes 111 perform the opposite function of tag conversion routines, i.e., receive as input an object and produce as output corresponding XML.
  • the response message encoder 113 uses the XML to create an
  • XML message e.g, a SOAP message.
  • the framework when a SOAP message is handed to the messaging framework, the framework performs the following steps: 1. Decode the message. 2. Convert any parameters to objects.
  • the present messaging framework provides for the separation and distinction of different aspects of remote method invocation, potentially allowing for these different aspects to be addressed by different programmers or developers. For example, an invoker developer would be concerned with what gets done in a request, a tag conversion developer would be concerned with what kinds of data can be passed in a request, and a protocol handler developer would be concerned with how messages get into and out of the messaging framework.
  • An important feature of the messaging framework is a "Tag Library" system in which special user defined modules (referred to sometimes hereafter as "type factories") are handed XML elements for conversion into objects.
  • a configuration is first built.
  • the configuration process begins by reading an ivory. config file, the content of which is specified in XML format.
  • the name of an XML top-level tag and its associated tag (toXML) converter are specified, as well as the name of a Java object and its type (fromXML) converter.
  • string which is a primitive type converter for a Java string
  • Product which is a user-defined type for a more complex object.
  • the messaging framework loads the ivory. config file and creates a tag library (converter library) having two types of converters: toXML converters, which map an object type to its corresponding converter, or "type factory," and fromXML converters, which map an XML tag and associated elements to its corresponding converter.
  • toXML converters which map an object type to its corresponding converter
  • type factory or "type factory”
  • fromXML converters which map an XML tag and associated elements to its corresponding converter.
  • the messaging framework converts objects from XML by matching the top-level XML tag with its associated converter.
  • Figure 3 an example of shown of how, using the tag library of Figure 2, a top-level Product element is converted from XML into a PreviewProduct using the PreviewProductType converter.
  • the messaging framework performs the following tasks in order to convert the XML representation of the Product into a PreviewProduct Java obj ect :
  • a complex type might contain simple types.
  • a converter for the complex type might use a converter for the simple type to help perform the conversion.
  • converter need not have knowledge of every element to perform a conversion; unknown elements may simply be passed along unconverted to a user defined module for the user defined module to handle. Considerable flexibility therefore results.
  • Appendix A shows a type converter that extracts text content and returns a String object.
  • the Ivory framework is not container dependent. Hence, although the
  • HTTP represents a convenient container with which the messaging framework may be used, any other desired system may be used.
  • Figure 4 shows the messaging framework used with email, in accordance with any of various email protocols.
  • the encoder/decoder 501 performs the functions of the encoder and decoder in the representation of Figure 1.
  • the encoder /decoder may represent the SOAP protocol encoding/decoding layer.
  • SOAP messages as remote method invocations, contain typed data. These data types are converted into objects before leaving the encoding/decoding layer 501. The responsibility for converting data types into objects falls on the type library 503.
  • the type library 503 performs the functions of tag conversion and type conversion in Figure 1.
  • the type library maps incoming XML data elements to type factories 505. When an XML element arrives that has an associated type factory, that factory builds a Java object from the XML.
  • the type factories are the converter routines of Figure 2.
  • the purpose of the messaging framework is to make remote method invocation easy to accomplish.
  • remote method invocation is used to invoke the services of request handlers.
  • a handler request is a remote object that exposes specific methods to the messaging framework. Maintaining these objects and routing incoming method calls is the responsibility of the handler registry 509.
  • the handler registry performs the invoker functions of Figure 1.
  • the handler objects correspond to the user defined modules of Figure 1.
  • the messaging framework does not require its handler objects to implement a fixed interface. Rather, all a handler object needs to expose a method to the messaging framework is to prefix the word "soap" to the front of any public method.
  • handler objects are loaded and bound into an invoker object.
  • the handler object undergoes introspection, in which all of the public methods of the handler object are inspected by name. Any methods starting with the keyword "soap" are exported for remote invocation purposes as illustrated in the code example of Appendix B.
  • the configuration services block 511 receives input from a configuration file as described in connection with Figure 2. Rather than using a simple text file for configuring the messaging framework, however, all framework objects are extracted from a configurator. In an exemplary embodiment, the configurator parses a DOM tree for configuration information.
  • FIG. 5 there is shown in Figure 5 an optional logging services block 515 that produces a log file 517, and an optional database connection manager 519.
  • the database connection manager allows handler objects to make database connections.
  • the database connection manager connects to a Ziplock database 521 associated with a ZiplockTM electronic software distribution server of the present assignee.
  • a code example illustrating invocation of the desired method is provided as

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

L'invention porte de manière générale sur une structure (101) de messagerie comprenant un dispositif (107) de conversion de type souple utilisable avec un service de téléappels via Internet. Lorsque la structure (101) reçoit un message, un décodeur (105) le décode, une routine (107) de conversion des marqueurs en convertit les paramètres en objets, localise le gestionnaire de messages approprié, et un module d'appel (107) requiert la méthode demandée dudit gestionnaire puis communique une valeur en retour (ou exception) via un message de réponse. Dans le cas du protocole SOAP par exemple, la valeur en retour (ou exception) est codée en XML, et inclue dans le message de réponse dudit protocole. La conversion (111) de type dynamique des paramètres en objets se fait à l'aide d'un système (107) de bibliothèque de marqueurs dans lequel (107) des modules (115) spéciaux définis par l'utilisateur (dits ' usine à types') sont les éléments traités par XLM devant être convertis en objets. Contrairement à l'architecture de type conversion stricte telle que la sérialisation classique d'objets, il n'existe pas de dépendance entre les entrées XML et les objets produits par l'usine à types. De plus l'usine ne doit plus extraire tout le contenu pendant la conversion, mais peut passer le contenu XML brut à l'objet construit en vue d'une utilisation ultérieure.
PCT/US2001/019007 2000-06-23 2001-06-12 Technique de conversion de types facilitant le teleappel de services WO2002001356A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP01946318A EP1305710A4 (fr) 2000-06-23 2001-06-12 Technique de conversion de types facilitant le teleappel de services

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US59951000A 2000-06-23 2000-06-23
US09/599,510 2000-06-23

Publications (2)

Publication Number Publication Date
WO2002001356A1 true WO2002001356A1 (fr) 2002-01-03
WO2002001356A9 WO2002001356A9 (fr) 2002-12-27

Family

ID=24399919

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2001/019007 WO2002001356A1 (fr) 2000-06-23 2001-06-12 Technique de conversion de types facilitant le teleappel de services

Country Status (2)

Country Link
EP (1) EP1305710A4 (fr)
WO (1) WO2002001356A1 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
FR2842623A1 (fr) * 2002-07-19 2004-01-23 Canon Kk Procede de traduction d'un message d'un premier langage de balisage dans un second langage de balisage
US7814211B2 (en) 2006-01-31 2010-10-12 Microsoft Corporation Varying of message encoding
US10698791B2 (en) 2018-07-28 2020-06-30 International Business Machines Corporation Handling request data with type safety in a remote service
CN114938387A (zh) * 2022-07-22 2022-08-23 浙江中控技术股份有限公司 一种数据传输方法、装置、系统及存储介质

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110647316B (zh) * 2019-09-23 2022-10-28 苏州达家迎信息技术有限公司 通用业务对象的生成方法、装置、计算机设备及存储介质

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5566302A (en) * 1992-12-21 1996-10-15 Sun Microsystems, Inc. Method for executing operation call from client application using shared memory region and establishing shared memory region when the shared memory region does not exist
US5606493A (en) * 1992-06-18 1997-02-25 International Business Machines Corporation Distributed applications processing network

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE69903711T2 (de) * 1998-02-26 2003-06-26 Sun Microsystems Inc Hinausgezögerte wiederherstellung von objekten und entfernte ladung für die mitteilung von ereignissen in einem verteilten system

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5606493A (en) * 1992-06-18 1997-02-25 International Business Machines Corporation Distributed applications processing network
US5566302A (en) * 1992-12-21 1996-10-15 Sun Microsystems, Inc. Method for executing operation call from client application using shared memory region and establishing shared memory region when the shared memory region does not exist

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP1305710A4 *

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
FR2842623A1 (fr) * 2002-07-19 2004-01-23 Canon Kk Procede de traduction d'un message d'un premier langage de balisage dans un second langage de balisage
US7555565B2 (en) 2002-07-19 2009-06-30 Canon Kabushiki Kaisha Method of translating a message from a first markup language into a second markup language
US7814211B2 (en) 2006-01-31 2010-10-12 Microsoft Corporation Varying of message encoding
US7925710B2 (en) 2006-01-31 2011-04-12 Microsoft Corporation Simultaneous API exposure for messages
US7949720B2 (en) 2006-01-31 2011-05-24 Microsoft Corporation Message object model
US10698791B2 (en) 2018-07-28 2020-06-30 International Business Machines Corporation Handling request data with type safety in a remote service
CN114938387A (zh) * 2022-07-22 2022-08-23 浙江中控技术股份有限公司 一种数据传输方法、装置、系统及存储介质
CN114938387B (zh) * 2022-07-22 2022-11-11 浙江中控技术股份有限公司 一种数据传输方法、装置、系统及存储介质

Also Published As

Publication number Publication date
WO2002001356A9 (fr) 2002-12-27
EP1305710A4 (fr) 2006-11-15
EP1305710A1 (fr) 2003-05-02

Similar Documents

Publication Publication Date Title
US6757899B2 (en) Dynamic CORBA gateway for CORBA and non-CORBA clients and services
US7127700B2 (en) Method and apparatus for developing web services using standard logical interfaces to support multiple markup languages
Duftler et al. Web services invocation framework (wsif)
US6792605B1 (en) Method and apparatus for providing web based services using an XML Runtime model to store state session data
US7028312B1 (en) XML remote procedure call (XML-RPC)
US7725906B2 (en) Method and device for executing a function with selection and sending of multiple results in a client-server environment
US20030233477A1 (en) Extensible infrastructure for manipulating messages communicated over a distributed network
Jepsen SOAP cleans up interoperability problems on the Web
US20040045004A1 (en) System for runtime web service to java translation
US20030182364A1 (en) Method and apparatus for requesting and performing batched operations for web services
US20040226027A1 (en) Application interface wrapper
US20040177335A1 (en) Enterprise services application program development model
US20080141139A1 (en) Architecture and Process for Presenting Application Content to Clients
CN111988171B (zh) 基于RESTful风格请求调用SOAP Web服务的方法、代理服务器及系统
WO2002001356A1 (fr) Technique de conversion de types facilitant le teleappel de services
Varga et al. Engineering web service invocations from agent systems
Zou et al. Towards a Webcentric Legacy System Migration Framework
JP4233775B2 (ja) データ通信方法、データ通信システムおよびプログラム
Zhao et al. Automated glue/wrapper code generation in integration of distributed and heterogeneous software components
Koftikian et al. Simple object access protocol (SOAP)
Dabhi et al. Developing Enterprise Solution with Web Services Integration
Gao A Java Implementation of the Simple Object Access Protocol
Hsiao et al. A new development environment for an event-based distributed system
Brooks An Introduction to Web Services
Tsenov WAN communication using SOAP protocol

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): JP

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR

121 Ep: the epo has been informed by wipo that ep was designated in this application
DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
AK Designated states

Kind code of ref document: C2

Designated state(s): JP

AL Designated countries for regional patents

Kind code of ref document: C2

Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR

COP Corrected version of pamphlet

Free format text: PAGES 1/5-5/5, DRAWINGS, REPLACED BY NEW PAGES 1/4-4/4; DUE TO LATE TRANSMITTAL BY THE RECEIVING OFFICE

WWE Wipo information: entry into national phase

Ref document number: 2001946318

Country of ref document: EP

WWP Wipo information: published in national office

Ref document number: 2001946318

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: JP

WWW Wipo information: withdrawn in national office

Ref document number: 2001946318

Country of ref document: EP