DOCSLIB.ORG

Code Generation Techniques for Developing Web Services For

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Code Generation Techniques for Developing Web Services For Published in the proceedings of the ACM SIGAPP SAC Conference, 2004 (Embedded Systems track) Code Generation Techniques for Developing Light-Weight XML Web Services for Embedded Devices ∗ Robert van Engelen Department of Computer Science Florida State University, Tallahassee, FL 32306-4530 [email protected] ABSTRACT ner prescribed by its definition, using XML based messages This paper presents specialized code generation techniques conveyed by Internet protocols.” [22]. This definition is often and runtime optimizations for developing light-weight XML refined to the use of the Web Services Description Language Web services for embedded devices. The optimizations are (WSDL) [23] for describing and advertising Web services, implemented in the gSOAP Web services development envi- SOAP [4] as the XML-based message packaging format, and ronment for C and C++. The system supports the industry- HTTP (HyperText Transport Protocol) [12] as the transport standard XML-based Web services protocols that are in- protocol. tended to deliver universal access to any networked appli- The ubiquity of HTTP and XML enables a high-level of cation that supports XML. With the standardization of the transport interoperability. The internal logic of an applica- Web services protocols and the availability of toolkits such as tion can be securely exposed to the Internet or local network gSOAP for developing embedded Web services, new oppor- as a service [20]. Such networked applications can actively tunities emerge to integrate embedded systems into larger participate in various forms of Internet transactions, rang- frameworks of interconnected applications and systems ac- ing from simple information services, such as checking flight cessing dynamic resources on the Web ranging from hand- status information with a cell phone, to more elaborate ap- held and embedded devices to databases, clusters, and Grids. plications such as Google searches [10], the controlling of “smart” buildings [17], and Grid systems [2, 9] for collabo- rative scientific research. However, the complexity and verbosity of XML Web ser- Keywords vices protocols creates a whole new set of design tradeoffs Networking, XML, Web Services, Embedded Systems and issues for developing Web services applications for em- bedded systems. Embedded systems rarely have enough memory and processing power to run an HTTP Web server, 1. INTRODUCTION SOAP engine, and XML parser. The verbosity of XML and Recent developments in Internet protocol standardization HTTP increases RAM usage, bandwidth requirements, and have led to the publication of a collection of XML-based pro- operating costs. Current Web services implementations do tocols that are meant to enhance cross-language and cross- not adequately address these issues [5, 6, 19]. platform interoperability, thereby encouraging systems in- This paper presents specialized code generation techniques tegration. More specifically, a Web service, as defined by and runtime optimizations for developing light-weight XML the W3C Web Services Architecture Working Group, is “a Web services for embedded devices. The techniques aim software system identified by a URI, whose public interfaces to reduce memory, network, and processing requirements and bindings are defined and described using XML. Its def- of SOAP/XML over HTTP. The optimizations are imple- inition can be discovered by other software systems. These mented in the gSOAP [21] Web services development envi- systems may then interact with the Web service in a man- ronment for C and C++, available from SourceForge and included in the IBM alphaWorks Web Services Tool Kit for ∗This material is based upon work supported by NSF Grants CCR-9904943, CCR-0105422, CCR-0208892, and by Mobile Devices (WSTKMD) [11]. DOE Grant DEFG02-02ER25543. Any opinions, findings, The remainder of this paper is organized as follows. Sec- and conclusions or recommendations expressed in this mate- tion 2 presents a brief overview of the most widely used rial are those of the author(s) and do not necessarily reflect systems and protocols for application-level communications. the views of the National Science Foundation. Several Web services implementations for embedded systems are also presented. Section 3 introduces Web services basics. Section 4 presents the gSOAP Web services toolkit followed in Section 5 by the presentation of the optimizations and Permission to make digital or hard copies of all or part of this work for code generation methods. The paper is summarized with personal or classroom use is granted without fee provided that copies are results in Section 6 and conclusions in Section 7. not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. To copy otherwise, to republish, to post on servers or to redistribute to lists, requires prior specific 2. RELATED WORK permission and/or a fee. SAC ’04, March 14-17, 2004, Nicosia, Cyprus Several systems and protocols have been proposed and Copyright 2004 ACM 1-58113-812-1/03/04 ...$5.00. developed since the early 1980s for inter-application data exchange. This section briefly reviews some of the most The IBM alphaWorks Web Services Tool Kit for Mobile widely used systems and protocols, and presents Web ser- Devices (WSTKMD) for Java, C, and C++ includes the vices development toolkits for embedded systems. kSOAP and gSOAP toolkits. The gSOAP toolkit [20, 21] Sun Microsystems’ RPC (Remote Procedure Call) com- is the only Web services development environment that in- piler generates code that is used by client and server ap- cludes a fully automated RPC compiler supporting pure plications to exchange data over a network. The runtime C and C++ Web services applications. The goal of the RPC parameter encoding and decoding mechanism is re- gSOAP project is to develop an easy-to-use portable Web ferred to as parameter marshaling and demarshaling, respec- services software development toolkit that fully automates tively. The marshaling routines convert application data the development and deployment cycle of efficient C/C++ into XDR (External Data Representation) [13] for transmis- Web services. The gSOAP compiler selectively generates sion. XDR does not support pointer-based data structures, code to limit application code size and to reduce run-time such as graphs. It only describes the most commonly used memory, network, and processing requirements of Web ser- data-types of high-level languages such as C so that applica- vice applications. The gSOAP 2.3 release is WSDL1.1 and tions written in these languages will be able to communicate. SOAP1.1/1.2 compliant and includes an HTTP1.0/1.1 Web CORBA is a platform-independent architecture for ORB server, an XML parser/generator, an RPC compiler, and (Object Request Brokerage) [15]. CORBA uses the IIOP a WSDL importer (compiler preprocessor). gSOAP 2.3 is (Internet Inter ORB Protocol) for data transmission be- portable to most platforms, including Linux, Unix (e.g. AIX, tween CORBA applications. CORBA’s IIOP supports a BSD, HP-UX, Irix, Solaris), Cygwin, Windows, Mac OS X, wide variety of data types that can be specified in the IDL Palm (OS 3,4 and 5), Pocket PC, Symbian, and cell phones. (Interface Description Language). CORBA is a heavy weight The gSOAP toolkit will be further discussed in Section 4. product and not very well suitable for embedded devices. Microsoft’s DCOM protocol is similar to IIOP and en- 3. WEB SERVICES BASICS ables COM objects on different Windows-based systems to Figure 1 shows the layered Web services architecture model. communicate. Although DCOM is a platform-independent protocol, it is mainly used within Windows environments. The transport layer is at the bottom of the model. The Sun Microsystems’ Java RMI (Remote Method Invoca- firewall-friendly HTTP (HyperText Transfer Protocol) tion) automatically marshals objects for communication be- and secure HTTPS are used to invoke Web services tween Java applications. There is no limit on the type of with HTTP POST request-response message exchanges. data objects that can be exchanged, since Java has built-in data serialization capabilities. Java supports the serializa- The packaging layer uses the XML-based SOAP protocol. tion of arbitrarily complex data structures such as graphs. Figure 2 depicts a SOAP 1.1 message transported with A large number of Web service implementations for var- HTTP/1.1. A SOAP message consists of an Enve- ious languages are available. A few of these support em- lope root element, an optional SOAP Header to encode bedded systems. Note that the “standard” embedded Web meta-information (such as authentication data, signa- servers [3, 18] do not support Web services standards but tures, routing points, and transaction tokens), encod- merely offer an HTTP interface. ing rules defining how messages should be processed, The following light-weight Web services implementations and an RPC representation in the SOAP Body that are suitable for embedded systems. Most implementations defines how to represent remote procedure calls and include an (embedded) HTTP Web server. They also typ- responses, such as the RPC method name and its pa- ically offer a library-based API (Application Programming rameters. The SOAP encoding style uses both scalar Interface) for SOAP/XML packaging. SOAP/XML mes- types (strings, integers, floats, and so on) and com- sages are constructed using a C++ or Java class library. pound types (structures and arrays) that can be used The micro-services framework [16] considers a subset of to carry application data. The values of these types the Web services protocols, with a scaled down Web server appear as XML elements within the method parame- and SOAP library with limited support for SOAP/XML ters of the SOAP Body. A SOAP Fault element (not data types. Only a subset of the SOAP/XML primitive shown) is used to carry error information to transfer types and compound types is supported. remote exceptions. The eSOAP [8] toolkit for C++ and Java, developed by EXOR International, is a proprietary SOAP implementation for embedded systems with an API based on a class library.
Load more

Recommended publications
  • CA Gen Integration Consuming REST Services – C Edition
    CA Gen Integration Consuming REST Services – C Edition Christian Kersters Broadcom Limited Web: www.broadcom.com Corporate Headquarters: San Jose, CA Broadcom Proprietary. © 2020 Broadcom. All rights reserved. Consuming REST Services – C Edition Revision History Revision Date Change Description V0.9 2020/11/12 Initial version V1.0 2020/11/17 Revised edition (integration of C. Jamar suggestions) Broadcom Proprietary. © 2020 Broadcom. All rights reserved. 1 Consuming REST Services – C Edition References CA Gen Integration Solutions, Christian Kersters, Broadcom, August 2017 https://community.broadcom.com/HigherLogic/System/DownloadDocumentFile.ashx?Docum entFileKey=4a401797-4dfe-4230-a031-273b908e57d3&forceDialog=0 Hello world: getting started with REST APIs https://www.genivia.com/dev.html#how-rest gSOAP User Guide https://www.genivia.com/doc/guide/html/index.html Richardson Maturity Model https://restfulapi.net/richardson-maturity-model/ Broadcom Proprietary. © 2020 Broadcom. All rights reserved. 2 Consuming REST Services – C Edition Contents Revision History ......................................................................................................................... 1 References ................................................................................................................................. 2 Contents ..................................................................................................................................... 3 1. Introduction ........................................................................................................................
    [Show full text]
  • Single-Node CUCM Single-Node IMP 10.201.203.76 10.201.203.75 10.201.203.67 10.201.203.72
    #CLUS CCIE Collaboration Techtorial Ben Ng, Exam PM, L@C, Cisco CX Ishan Sambhi, CSE, Cisco CX TECCCIE-3503 #CLUS Agenda • Session 1: CCIE® Program Overview • Session 2: CCIE Collaboration Overview • Session 3: CCIE Collaboration Modular Lab Exams • Session 4: Lab Exam Diagnostic Module with Case Studies • Session 5: Lab Exam Troubleshooting Module with Case Studies • Session 6: Lab Exam Configuration Module with Case Studies • Session 7: Exam Preparation Tips, In-Lab Strategies, and Q&A #CLUS TECCCIE-3503 © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 3 Cisco Webex Teams Questions? Use Cisco Webex Teams to chat with the speaker after the session How 1 Find this session in the Cisco Live Mobile App 2 Click “Join the Discussion” 3 Install Webex Teams or go directly to the team space 4 Enter messages/questions in the team space Webex Teams will be moderated cs.co/ciscolivebot#TECCCIE-3503 by the speaker until June 16, 2019. #CLUS © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 4 Session 1: CCIE Program Overview Cisco CCIE Certifications CCIE Track Major Skills R&S Configure and troubleshoot complex converged networks Security Configure complex, end-to-end secure networks, troubleshoot environments, and anticipate and respond to network attacks Service Provider Configure and troubleshoot advanced technologies to support service provider networks Collaboration Design, implement, integrate, and troubleshoot complex collaboration networks Wireless Plan, design, implement, operate, and troubleshoot wireless network and mobility infrastructure Data Center Configure and troubleshoot Cisco Data Center technologies including DC infrastructure, compute and virtualization. #CLUS TECCCIE-3503 © 2019 Cisco and/or its affiliates.
    [Show full text]
  • SOAP Toolkits for Web Services Developer Guide
    SOAP Toolkits for Web Services Developer Guide CyberSource Contact Information For general information about our company, products, and services, go to http://www.cybersource.com. For sales questions about any CyberSource Service, email [email protected] or call 650-432-7350 or 888-330-2300 (toll free in the United States). For support information about any CyberSource Service, visit the Support Center: http://www.cybersource.com/support Copyright © July 2020 CyberSource Corporation. All rights reserved. CyberSource Corporation (“CyberSource”) furnishes this document and the software described in this document under the applicable agreement between the reader of this document (“You”) and CyberSource (“Agreement”). You may use this document and/or software only in accordance with the terms of the Agreement. Except as expressly set forth in the Agreement, the information contained in this document is subject to change without notice and therefore should not be interpreted in any way as a guarantee or warranty by CyberSource. CyberSource assumes no responsibility or liability for any errors that may appear in this document. The copyrighted software that accompanies this document is licensed to You for use only in strict accordance with the Agreement. You should read the Agreement carefully before using the software. Except as permitted by the Agreement, You may not reproduce any part of this document, store this document in a retrieval system, or transmit this document, in any form or by any means, electronic, mechanical, recording, or otherwise, without the prior written consent of CyberSource. Restricted Rights Legends For Government or defense agencies. Use, duplication, or disclosure by the Government or defense agencies is subject to restrictions as set forth the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 and in similar clauses in the FAR and NASA FAR Supplement.
    [Show full text]
  • Application of Web Services to a Simulation Framework Matthew Bennink Clemson University, [email protected]
    Clemson University TigerPrints All Theses Theses 12-2008 Application of Web Services to a Simulation Framework Matthew Bennink Clemson University, [email protected] Follow this and additional works at: https://tigerprints.clemson.edu/all_theses Part of the Computer Sciences Commons Recommended Citation Bennink, Matthew, "Application of Web Services to a Simulation Framework" (2008). All Theses. 500. https://tigerprints.clemson.edu/all_theses/500 This Thesis is brought to you for free and open access by the Theses at TigerPrints. It has been accepted for inclusion in All Theses by an authorized administrator of TigerPrints. For more information, please contact [email protected]. Application of Web Services to a Simulation Environment A Thesis Presented to the Graduate School of Clemson University In Partial Fulfillment of the Requirements for the Degree Master of Science Computer Engineering by Matthew Scott Bennink December 2008 Accepted by: Dr. Richard Brooks, Committee Chair Dr. Adam Hoover Dr. Christopher Griffin Abstract The Joint Semi-Automated Forces (JSAF) simulator is an excellent tool for military training and a great testbed for new SAF behaviors. However, it has the drawback that behaviors must be ported into its own Finite State Machine (FSM) language. Web Services is a growing technology that seamlessly connects service providers to service consumers. This work attempts to merge these two technologies by modeling SAF behaviors as web services. The JSAF simulator is then modeled as a web service consumer. This approach allows new Semi-Automated Forces (SAF) behaviors to be developed inde- pendently of the simulator, which provides the developer with greater flexibility when choosing a programming language, development environment, and development platform.
    [Show full text]
  • Web Exploit Finder
    WEF – Web Exploit Finder Dokumentation zum Praktikum Softwaretechnik SS 2006 Medieninformatik Hochschule der Medien, Stuttgart Thomas Müller (tm026) Benjamin Mack (bm022) Mehmet Arziman (ma018) Betreut von: Prof. Dr. Roland Schmitz WEF – Web Exploit Finder Praktikum Softwaretechnik SS 2006 Inhaltsverzeichnis 1 Motivation........................................................................................ 3 2 Beschreibung der Idee .................................................................... 3 3 Einschränkungen.............................................................................. 6 4 Die System-Architektur.................................................................... 6 4.1 Management-Konsole.....................................................................7 4.1.1 Schnittstellen der Management-Konsole......................................8 4.1.2 Business-Logik und Datenmodell (EJB 3.0) ..............................8 4.1.3 WebGUI (JSF) .....................................................................11 4.1.4 SOAP Web-Services (XFire)..................................................... 14 4.1.5 VmControl Java Modul und VMware Skripte ............................. 17 4.2 VM Wirt...................................................................................... 23 4.2.1 Server-Installation................................................................. 23 4.2.2 Windows XP Image Template (Prototyp)................................... 23 4.3 Browser Control...........................................................................24
    [Show full text]
  • AC Library for Clients of ONVIF Network Video
    UMOC – A C Library for Clients of ONVIF Network Video Transmitters Library Design and Device Discovery Support Sérgio F. Lopes1, Sérgio Silva2, José Cabral1 and João L. Monteiro1 1Centro Algoritmi, School of Engineering, University of Minho, Guimarães, Portugal 2 Keywords: Video Surveillance and Control, ONVIF, SOAP, WS-Discovery, WS-Security, Web Services, NVT. Abstract: Video surveillance and control systems are becoming increasingly important as video analysis techniques evolve. The interoperability of IP video equipment is a critical problem for surveillance systems and other video application developers. Open Network Video Interface Forum (ONVIF) is one of the two specifications addressing the standardization of networked devices interface, but it is a complex specification and difficult to implement. This paper describes a library that helps to develop clients of ONVIF video cameras, by taking advantage of opportunities to abstract useless details and to provide higher-level functionalities. The library architecture is explained and it is shown how it can be used to implement operations and features that present challenges to developers. The module supporting Device Discovery is addressed. We demonstrate how the library reduces the complexity, without affecting flexibility. The work presented has been validated by an industry partner. 1 INTRODUCTION Web Services (WS) enable machine interoperability over a network by defining a Since Internet Protocol (IP) digital cameras became standard way to describe service operations, data less expensive, video surveillance and control format and network protocol. Usually they are based systems are becoming increasingly important as on open and well-established standards such as video analysis techniques evolve. Furthermore, this HTTP for information transport and XML for data equipment comes with digital outputs and inputs, serialization.
    [Show full text]
  • Parse Xml Schema C
    Parse Xml Schema C Merry luminesced ostensibly as untreasured Wash etymologise her outcrops crop excelsior. Lateritic Andreas peises no settlingexclaiming snowily subirrigate or flamming chastely any after transcendency. Reza ensconces commodiously, quite retiary. Georgy remains shrewish after Harold The xml schema to the unmarshaller will match those ways are legal structure of classes in xml content and spark xml To the modules where the XML files that conform as the XSD are brought and used. The schema is same directory as it work correctly when parsing styles, the processor to check is. The schema into individual components like it is a sax. Looking past the following XML what text value there we find the path ace. The schema of these classes using the previous tip dialog box appears as web and parses. Parsing XML file is unique very basic programming requirement. As parsing callbacks themselves are parsed and parses the text editor on all types of validation is superior to use for high parsing with xml schema comes in. What this An XML File And thread Do several Open response How-To Geek. A Xerces-C is a validating XML parser written up a portable subset of C parsefile where file. What program opens XML files? Mac OS X and AIX Supported compilers Visual C GNU g Sun C HP. Validating XML using XSD Knoldus Blogs. May not parsing large schemas parse xml parsed structs require other than the answers. XML Schema Simple Elements W3Schools. How to parse our newsletter to import xml schemas reference to take care of xml document against its content useful with qt applications xml schemas.
    [Show full text]
  • Gsoap Toolkit Fact Sheet for Version Release 2.8.0 and Up
    gSOAP toolkit fact sheet for version release 2.8.0 and up - Intended for C and C++ (with optional use of STL containers) - Client and server (HTTP/S Web server and SOAP/XML engine included) - High-performance Web services (measured with 2.2KB XML messages over HTTP): 3241 roundtrip calls per second on AMD FX-53 2.4GHz, 64-bit Linux 2.6.5 2990 roundtrip calls per second on AMD Opteron 148 2.2GHz, 64-bit Linux 2.6.5 2265 roundtrip calls per second on 2x Itanium2 1.4GHz, Linux 2.6.9 IA-64 1936 roundtrip calls per second on Pentium4 3GHz (w/o HT), Linux 2.6.5 - Small footprint: Only 73KB code and 2KB data for XMethods' delayed stock-quote app on Pentium4, Linux 2.6.5, gcc 3.3.3 -O1 Only 100KB code and 2KB data for Google API app on Pentium4, Linux 2.6.5, gcc 3.3.3 -O1 - Portable open-source C/C++ code, field-tested on the following platforms: Windows Win32/Win64 (including NT, 2000, XP, Vista, Windows 7), MS-DOS (limited), and Cygwin Linux (RedHat, SuSE, and any other "standard" Linux distro), Unix (Solaris, HP-UX, FreeBSD, Irix, QNX, AIX, 64bit TRU64, and other) Mac OS X (universal) OpenVMS Tandem NonStop Small and embedded OS (VxWorks, WinCE, Palm OS, Symbian). - Testing and debugging: Automatic echo test server code generation (soapcpp2 -T option) Automatic request/response sample SOAP/XML message generation for testing Automatic leak detection in debug mode SOAP 1.1 and 1.2 messaging tested and validated against "soapbuilders Interoperability round 2 A to C" Tested against eBay services, Amazon services, Google services, Wolfram services,
    [Show full text]
  • Web Services Developer's Guide Copyright © 2001–2019 Micro Focus Or One of Its Affiliates
    Solutions Business Manager Web Services Developer's Guide Copyright © 2001–2019 Micro Focus or one of its affiliates. The only warranties for products and services of Micro Focus and its affiliates and licensors (“Micro Focus”) are as may be set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Micro Focus shall not be liable for technical or editorial errors or omissions contained herein. The information contained herein is subject to change without notice. Except as specifically indicated otherwise, this document contains confidential information and a valid license is required for possession, use or copying. If this work is provided to the U.S. Government, consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed under vendor's standard commercial license. Part number: Product version: 11.7 Publication date: 2019-11-01 2 Solutions Business Manager (SBM) Table of Contents Chapter 1: Preface .......................................................................................... 13 Chapter 2: Getting Started ................................................................................. 15 About the SBM Application Engine Web Services API .......................................... 15 About Web Services ....................................................................................... 15 SOAP Requests ............................................................................................
    [Show full text]
  • Extr-EXOS Warranty Regarding Use of Open Source Software Open
    Open Source Declaration for: extr-EXOS Software Release: Versions: 30.6 Release Date: 2020-03-13 This document contains attributions, licenses, and notices for free and open source software (Collectively FOSS) used within this product. If you have any questions or wish to receive a copy of any FOSS source code to which you may be entitled, please contact us at [email protected]. Extreme Networks, Inc 6480 Via Del Oro San Jose, California 95119 Phone / +1 408.904.7002 Toll-free / + 1 888.257.3000 www.extremenetworks.com © 2019 Extreme Networks, Inc. All rights reserved. Extreme Networks, the Extreme Networks logo, and "Project Names" are trademarks or registered trademarks of Extreme Networks, Inc. in the United States and/or other countries. All other names, registered trademarks, trademarks, and service marks are property of their respective owners. For additional information on Extreme Networks trademarks, see www.extremenetworks.com/company/legal/trademarks Warranty Regarding Use of Open Source Software This FOSS is provided to you on an "as is" basis, and Extreme Networks makes no representations or warranties for the use of this code by you independent of any Extreme Networks provided software or services. Refer to the licenses and copyright notices listed below for each package for any specific license terms that apply to each software bundle. The licenses listed below define the warranty, if any, from the associated authors or licensors. Extreme Networks specifically disclaims any warranties for defects caused caused by altering or modifying any FOSS or the products' recommended configuration. You have no warranty or indemnification claims against Extreme Networks in the event that the FOSS infringes the intellectual property rights of a third party.
    [Show full text]
  • Secure Web Services with Globus GSI and Gsoap
    Secure Web Services with Globus GSI and gSOAP Giovanni Aloisio1, Massimo Cafaro1, Daniele Lezzi1, and Robert van Engelen2 1 High Performance Computing Center University of Lecce/ISUFI, Italy [email protected] [email protected] [email protected] 2 Computer Science Department Florida State University, USA [email protected] Abstract. In this paper we describe a plug-in for the gSOAP Toolkit that allows development of Web Services exploiting the Globus Secu- rity Infrastructure (GSI). Our plug-in allows the development of GSI enabled Web Services and clients, with full support for mutual authen- tication/authorization, delegation of credentials and connection caching. The software provides automatic, transparent transport-level security for Web Services and is freely available. 1 Introduction Recently, the Web Services framework [1] has gained considerable attention. Based on XML (Extensible Markup Language) [2] technologies like SOAP (Sim- ple Object Access Protocol) [3], WSDL (Web Services Description Language)[4], WSFL (Web Services Flow Language) [5] and UDDI (Universal Description, Dis- covery and Integration) [6], the Web Services approach to distributed computing represents the latest evolution supporting the creation, deployment and dynamic discovery of distributed applications. As a matter of fact, the Internet and the Web allow to publish and retrieve documents easily, and to access a number of commercial, public and e-government services. However, the focus on the usage of such services is now been shifted from people to software applications. The Web Services framework makes this shift possible, due to the convergence of two key technologies: the Web, with its well known and universally accepted set of standard protocols for communication, and Service-Oriented computing where both data and business logic is exposed through a programmable inter- face e.g.
    [Show full text]
  • Gsoap 2.7.10 User Guide
    gSOAP 2.7.10 User Guide Robert van Engelen Florida State University and Genivia, Inc. [email protected] & [email protected] February 4, 2008 Contents 1 Introduction 8 1.1 Getting Started . 8 1.2 Your First Web Service Client Application . 9 1.3 Your First Web Service in CGI . 10 1.4 Features . 11 2 Notational Conventions 13 3 Differences Between gSOAP Versions 2.4 (and Earlier) and 2.5 13 4 Differences Between gSOAP Versions 2.1 (and Earlier) and 2.2 14 5 Differences Between gSOAP Versions 1.X and 2.X 14 6 Interoperability 16 7 Quick User Guide 17 7.1 How to Use the gSOAP Stub and Skeleton Compiler to Build SOAP Clients . 18 7.1.1 Example . 19 7.1.2 Namespace Considerations . 23 7.1.3 Example . 24 7.1.4 How to Generate C++ Client Proxy Classes . 25 7.1.5 XSD Type Encoding Considerations . 27 7.1.6 Example . 28 7.1.7 How to Change the Response Element Name . 29 7.1.8 Example . 29 1 7.1.9 How to Specify Multiple Output Parameters . 30 7.1.10 Example . 30 7.1.11 How to Specify Output Parameters With struct/class Compound Data Types ...................................... 31 7.1.12 Example . 31 7.1.13 How to Specify Anonymous Parameter Names . 34 7.1.14 How to Specify a Method with No Input Parameters . 35 7.1.15 How to Specify a Method with No Output Parameters . 35 7.2 How to Use the gSOAP Stub and Skeleton Compiler to Build SOAP Web Services 36 7.2.1 Example .
    [Show full text]