DOCSLIB.ORG

Session 3: XML Information Processing

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Extreme Java G22.3033-007 Session 3 - Sub-Topic 4 XML Information Processing Dr. Jean-Claude Franchitti New York University Computer Science Department Courant Institute of Mathematical Sciences 1 Agenda Q XML applications development tools for Java Q XML application Development using the XML Java APIs Q Java-based XML application support frameworks Q Advanced XML Parser Technology Q JDOM: Java-Centric API for XML Q JAXP: Java API for XML Processing Q Parsers comparison Q Latest W3C APIs and Standards for Processing XML Q XML Infoset, DOM Level 3, Canonical XML Q XML Signatures, XBase, XInclude Q XML Schema Adjuncts Q Java-Based XML Data Processing Frameworks 2 1 XML-Based Software Development Q Business Engineering Methodology Q Language + Process + Tools Q e.g., Rational Unified Process (RUP) Q XML Application Development Infrastructure Q Metadata Management (e.g., XMI) Q XML APIs (e.g., JAXP, JAXB) Q XML Tools (e.g., XML Editors, XML Parsers) Q XML Applications: Q Application(s) of XML Q XML-based applications/services (markup language mediators) Q MOM & POP Q Other Services (e.g., persistence, transaction, etc.) Q Application Infrastructure Frameworks 3 More on XML Information Modeling Q Using UML use cases to support the development of DTDs and XML Schemas Q Establish linking relationship Q See Family tree application of XML 4 2 Part I XML Application Development Tools for Java 5 Java-enabled XML Technologies Q XML provides a universal syntax for Java semantics (behavior) Q Portable, reusable data descriptions in XML Q Portable Java code that makes the data behave in various ways Q XML standard extension Q Basic plumbing that translates XML into Java Q parser, namespace support in the parser, simple API for XML (SAX), and document object model (DOM) Q XML data binding standard extension 6 3 XML Processors Characteristics Q An XML engine is a general purpose XML data processor Q An XML processor/parser is a software engine that checks the syntax (well-formedness)of XML documents Q If a schema (or DTD) is included, the parser can (optionally) validate the correctness of XML documents’ structure against it Q A parser reads the XML document’s information and makes it accessible to the XML application via a standard API 7 Common XML APIs Q Document Object Model (DOM) API Q Tree structure-based API Q Issued as a W3C recommendation (10/98) Q See Session 5 Sub-Topic 1 Presentation Q Simple API for XML (SAX) Q Event-driven API Q Developed by David Megginson Q ElementHandler API Q Event-driven proprietary API provided by IBM’s XML4J Q Pure Java APIs: JDOM (Open Source) and JAXP 8 4 Java API Packages Q java.xml.parsers Q The JAXP APIs, which provide a common interface for different vendors' SAX and DOM parsers. Q Two vendor-neutral factory classes: SAXParserFactory and DocumentBuilderFactory that give you a SAXParser and a DocumentBuilder, respectively. The DocumentBuilder, in turn, creates DOM-compliant Document object. Q org.w3c.dom Q Defines the Document class (a DOM), as well as classes for all of the components of a DOM. Q org.xml.sax Q Defines the basic SAX APIs. Q jaxax.xml.transform 9 Q Defines the XSLT APIs that let you transform XML into other forms. Simple API for XML (SAX) Parsing APIs 10 5 SAX API Packages Q org.xml.sax Q Defines the SAX interfaces. Q org.xml.sax.ext Q Defines SAX extensions that are used when doing more sophisticated SAX processing, for example, to process a document type definitions (DTD) or to see the detailed syntax for a file. Q org.xml.sax.helpers Q Contains helper classes that make it easier to use SAX -- for example, by defining a default handler that has null-methods for all of the interfaces, so you only need to override the ones you actually want to implement. Q javax.xml.parsers Q Defines the SAXParserFactory class which returns the SAXParser. Also defines exception classes for reporting errors. 11 DOM Parsing APIs 12 6 DOM API Packages Q org.w3c.dom Q Defines the DOM programming interfaces for XML (and, optionally, HTML) documents, as specified by the W3C. Q javax.xml.parsers Q Defines the DocumentBuilderFactory class and the DocumentBuilder class, which returns an object that implements the W3C Document interface. The factory that is used to create the builder is determined by the javax.xml.parsers system property, which can be set from the command line or overridden when invoking the newInstance method. This package also defines the ParserConfigurationException class for reporting errors. 13 XSLT APIs 14 7 XSLT API Packages Q See Session 3 handout on “Processing XML Documents in Java Using XPath and XSLT” Q javax.xml.transform Q Defines the TransformerFactory and Transformer classes, which you use to get a object capable of doing transformations. After creating a transformer object, you invoke its transform() method, providing it with an input (source) and output (result). Q javax.xml.transform.dom Q Classes to create input (source) and output (result) objects from a DOM. Q javax.xml.transform.sax Q Classes to create input (source) from a SAX parser and output (result) objects from a SAX event handler. Q javax.xml.transform.stream Q Classes to create input (source) and output (result) objects from an I/O stream. 15 JAXP and Associated XML APIs Q JAXP: Java API for XML Parsing Q Common interface to SAX, DOM, and XSLT APIs in Java, regardless of which vendor's implementation is actually being used. Q JAXB: Java Architecture for XML Binding Q Mechanism for writing out Java objects as XML (marshalling) and for creating Java objects from such structures (unmarshalling). Q JDOM: Java DOM Q Provides an object tree which is easier to use than a DOM tree, and it can be created from an XML structure without a compilation step. Q JAXM: Java API for XML Messaging Q Mechanism for exchanging XML messages between applications. Q JAXR: Java API for XML Registries Q Mechanism for publishing available services in an external registry, 16 and for consulting the registry to find those services. 8 Content of Jar Files Q jaxp.jar (interfaces) Q javax.xml.parsers Q javax.xml.transform Q javax.xml.transform.dom Q javax.xml.transform.sax Q javax.xml.transform.stream Q crimson.jar (interfaces and helper classes) Q org.xml.sax Q org.xml.sax.helpers Q org.xml.sax.ext Q org.w3c.dom Q xalan.jar (contains all of the above implementation classes) 17 Sample XML parsers and engines Q XML parsers Q RXP, Dan Connolly’s XML parser, XML-Toolkit, LTXML, expat, TCLXML, xparse, XP, DataChannel XPLparser (DXP), XML:Parse, PyXMLTok, Lark, Microsoft’s XML parser, IBM’s XML for Java, Apache’s Xerces-J, Aefred, xmlproc, xmllib, Windows foundation classes, Java Project X Parser (Crimson), OpenXML Parser, Oracle XML Parser, etc. Q SGML/XML parsers Q SGMLSpm, SP 18 9 Sample XML Parsers and Engines (continued) Q XML middleware: Xpublish (Media Design), XML middleware 1.0 Q DSSSL engines: Jade 1.1, DAE SDK, DAE Server SDK Q XSL processors: Sparse, Microsoft XSL processor, doproc, xslj, LotusXSL, Xalan, XSL:P Q XLink processors: xmllinks 19 Comprehensive List of XML Processors Q A comprehensive list of parsers is available at http//www.xmlsoftware.com/parsers Q Includes links to latest product pages Q Includes Version numbers, Licensing information, and Platform details Q Research work being done around MetaParsers and parallel XML parsers 20 10 Mainstream Java-Based XML Processors Q Sun’s Java Project X Parser Q Donated on April 13, 2000 to the Apache’s XML Project under the name “Crimson” Q Apache’s XercesJ Q XercesJ is strongly recommended for this course Q Oracle’s XML Parser for Java 21 Other Java-Based XML Processors Q Sun’s JAXP Q Jason Hunter and Brett McLaughlin’s OpenSource JDOM Q IBM Alphaworks’s XML for Java (XML4J) Q Based on the Apache Xerces XML Parser Q DataChannel’s XJParser 22 11 XML Data Binding Standard Extension Q Aims to automatically generate substantial portions of the Java platform code that processes XML data Q A Sun project, codenamed “Adelard” Q See JSR-31 XML Data Binding Specification Q see http://java.sun.com/xml/jaxp-1.0.1/docs/binding/DataBinding.html 23 Part II XML Application Development Using the XML Java APIs 24 12 Typical XML Processor Installation Q Pick a processor based on the features it provides to match your requirements Q Download and install the latest (or supported) version of the JDK from http://www.javasoft.com Q Install the XML processor Q Update the PATH and CLASSPATH variables as needed, and test the processor 25 Reading XML Documents Q Use Apache’s XercesJ or Alphaworks’ XML Parser for Java Q The “SimpleParse.java” application provided in section 2.4 of “XML and Java” will need to be adapted to support the latest version of the parsers Q We suggest looking at the source for the sample applications located in XercesSamples.jar Q For testing, use XML and Java’s sample document or the “personal.xml” sample XML document provided with XML4J 26 13 Presenting XML Documents Using Java Tools Q Presenting an XML document requires processing of the XML document by accessing its internal stucture Q An XML document’s structure can be accessed using the various XML APIs Q Various third party tools have been implemented using such APIs to apply XSL style sheets to XML documents and generate HTML output (e.g., Xalan, LotusXSL) 27 XML Data Exchange Protocols Q Message format alternatives Q Text-based (e.g., EDI, RFC822, SGML, XML) Q Binary (e.g., ASN.1, CORBA/IIOP) Q See XML and Java sections 7.2, and 7.4 Q An API that provide a common interface to work with EDI or XML/EDI objects is supported
Recommended publications
  • JAXB Release Documentation JAXB Release Documentation Table of Contents

    JAXB Release Documentation JAXB Release Documentation Table of Contents

    JAXB Release Documentation JAXB Release Documentation Table of Contents Overview .......................................................................................................................... 1 1. Documentation ....................................................................................................... 1 2. Software Licenses ................................................................................................... 1 3. Sample Apps .......................................................................................................... 2 3.1. Using the Runtime Binding Framework ............................................................ 2 Release Notes .................................................................................................................... 6 1. Java™ 2 Platform, Standard Edition (J2SE™) Requirements .......................................... 7 2. Identifying the JAR Files ......................................................................................... 7 3. Locating the Normative Binding Schema .................................................................... 7 4. Changelog ............................................................................................................. 7 4.1. Changes between 2.3.0.1 and 2.4.0 .................................................................. 7 4.2. Changes between 2.3.0 and 2.3.0.1 .................................................................. 7 4.3. Changes between 2.2.11 and 2.3.0 ..................................................................
  • Fun Factor: Coding with Xquery a Conversation with Jason Hunter by Ivan Pedruzzi, Senior Product Architect for Stylus Studio

    Fun Factor: Coding with Xquery a Conversation with Jason Hunter by Ivan Pedruzzi, Senior Product Architect for Stylus Studio

    Fun Factor: Coding With XQuery A Conversation with Jason Hunter by Ivan Pedruzzi, Senior Product Architect for Stylus Studio Jason Hunter is the author of Java Servlet Programming and co-author of Java Enterprise Best Practices (both O'Reilly Media), an original contributor to Apache Tomcat, and a member of the expert groups responsible for Servlet, JSP, JAXP, and XQJ (XQuery API for Java) development. Jason is an Apache Member, and as Apache's representative to the Java Community Process Executive Committee he established a landmark agreement for open source Java. He co-created the open source JDOM library to enable optimized Java and XML integration. More recently, Jason's work has focused on XQuery technologies. In addition to helping on XQJ, he co-created BumbleBee, an XQuery test harness, and started XQuery.com, a popular XQuery development portal. Jason presently works as a Senior Engineer with Mark Logic, maker of Content Interaction Server, an XQuery-enabled database for content. Jason is interviewed by Ivan Pedruzzi, Senior Product Architect for Stylus Studio. Stylus Studio is the leading XML IDE for XML data integration, featuring advanced support for XQuery development, including XQuery editing, mapping, debugging and performance profiling. Ivan Pedruzzi: Hi, Jason. Thanks for taking the time to XQuery behind a J2EE server (I have a JSP tag library talk with The Stylus Scoop today. Most of our readers for this) but I’ve found it easier to simply put XQuery are familiar with your past work on Java Servlets; but directly on the web. What you do is put .xqy files on the could you tell us what was behind your more recent server that are XQuery scripts to produce XHTML interest and work in XQuery technologies? pages.
  • Merchandise Planning and Optimization Licensing Information

    Merchandise Planning and Optimization Licensing Information

    Oracle® Retail Merchandise Planning and Optimization Licensing Information July 2009 This document provides licensing information for all the third-party applications used by the following Oracle Retail applications: ■ Oracle Retail Clearance Optimization Engine ■ Oracle Retail Markdown Optimization ■ Oracle Retail Place ■ Oracle Retail Plan ■ Oracle Retail Promote (PPO and PI) Prerequisite Softwares and Licenses Oracle Retail products depend on the installation of certain essential products (with commercial licenses), but the company does not bundle these third-party products within its own installation media. Acquisition of licenses for these products should be handled directly with the vendor. The following products are not distributed along with the Oracle Retail product installation media: ® ■ BEA WebLogic Server (http://www.bea.com) ™ ■ MicroStrategy Desktop (http://www.microstrategy.com) ■ MicroStrategy Intelligence Server™ and Web Universal (http://www.microstrategy.com) ® ■ Oracle Database 10g (http://www.oracle.com) ® ■ Oracle Application Server 10g (http://www.oracle.com) ® ■ Oracle Business Intelligence Suite Enterprise Edition Version 10 (http://www.oracle.com) ■ rsync (http://samba.anu.edu.au/rsync/). See rsync License. 1 Softwares and Licenses Bundled with Oracle Retail Products The following third party products are bundled along with the Oracle Retail product code and Oracle has acquired the necessary licenses to bundle the software along with the Oracle Retail product: ■ addObject.com NLSTree Professional version 2.3
  • On the Integrity and Trustworthiness of Web Produced Data

    On the Integrity and Trustworthiness of Web Produced Data

    CORE Metadata, citation and similar papers at core.ac.uk Provided by Open Repository of the University of Porto On the Integrity and Trustworthiness of web produced data Luís A. Maia Mestrado Integrado em Engenharia de Redes e Sistemas Informáticos Departamento de Ciência de Computadores 2013 Orientador Professor Doutor Manuel Eduardo Carvalho Duarte Correia, Professor Auxiliar do Departamento de Computadores, Faculdade de Ciências da Universidade do Porto Todas as correções determinadas pelo júri, e só essas, foram efetuadas. O Presidente do Júri, Porto, ______/______/_________ Acknowledgments I would like to express my appreciation for the help of my supervisor in researching and bringing different perspectives and to thank my family, for their support and dedication. 3 Abstract Information Systems have been a key tool for the overall performance improvement of administrative tasks in academic institutions. While most systems intend to deliver a paperless environment to each institution it is recurrent that document integrity and accountability is still relying on traditional methods such as producing physical documents for signing and archiving. While this method delivers a non-efficient work- flow and has an effective monetary cost, it is still the common method to provide a degree of integrity and accountability on the data contained in the databases of the information systems. The evaluation of a document signature is not a straight forward process, it requires the recipient to have a copy of the signers signature for comparison and training beyond the scope of any office employee training, this leads to a serious compromise on the trustability of each document integrity and makes the verification based entirely on the trust of information origin which is not enough to provide non-repudiation to the institutions.
  • XML Signature/Encryption — the Basis of Web Services Security

    XML Signature/Encryption — the Basis of Web Services Security

    Special Issue on Security for Network Society Falsification Prevention and Protection Technologies and Products XML Signature/Encryption — the Basis of Web Services Security By Koji MIYAUCHI* XML is spreading quickly as a format for electronic documents and messages. As a consequence, ABSTRACT greater importance is being placed on the XML security technology. Against this background research and development efforts into XML security are being energetically pursued. This paper discusses the W3C XML Signature and XML Encryption specifications, which represent the fundamental technology of XML security, as well as other related technologies originally developed by NEC. KEYWORDS XML security, XML signature, XML encryption, Distributed signature, Web services security 1. INTRODUCTION 2. XML SIGNATURE XML is an extendible markup language, the speci- 2.1 Overview fication of which has been established by the W3C XML Signature is an electronic signature technol- (WWW Consortium). It is spreading quickly because ogy that is optimized for XML data. The practical of its flexibility and its platform-independent technol- benefits of this technology include Partial Signature, ogy, which freely allows authors to decide on docu- which allows an electronic signature to be written on ment structures. Various XML-based standard for- specific tags contained in XML data, and Multiple mats have been developed including: ebXML and Signature, which enables multiple electronic signa- RosettaNet, which are standard specifications for e- tures to be written. The use of XML Signature can commerce transactions, TravelXML, which is an EDI solve security problems, including falsification, spoof- (Electronic Data Interchange) standard for travel ing, and repudiation. agencies, and NewsML, which is a standard specifica- tion for new distribution formats.
  • Major Open Source ILS Products

    Major Open Source ILS Products

    Chapter 3 Major Open Source ILS Products t least four open source ILS products are available system, called Catalist, which was not compliant with the today: Koha, Evergreen, and OPALS. (see table looming Y2K issue. Rather than purchase a commercial A4). While there may be some additional products, system, HLT contracted with a consulting company named these four have emerged as the most widely implemented Katipo Communications to develop a new Web-based sys- and serve as good examples of the current state of the tem. They named this new system Koha, the Maori word art of the open source ILS. While each of these products for gift or donation, and released it as open source, allow- bears a great deal of similarity in approach, they also dif- ing libraries anywhere to use and help develop and sup- fer in features and functionality and in their appeal to port the software. The HLT libraries began using Koha on different types of libraries This section provides detailed January 1, 2000. information regarding each of these systems. A fairly quiet period followed the initial release of Koha, with a few individuals and libraries picking up on the system. No groundswell of interest resulted right away. The initial version of Koha was quite adequate for History and Background three libraries of HLT that together served a commu- Koha nity of about 30,000 residents with a collection of about 80,000 volumes. At that point, Koha did not have some Koha claims the status of being the first open source of the features considered mandatory for most libraries— November/December 2008 November/December library automation system.
  • Sams Teach Yourself XML in 21 Days

    Sams Teach Yourself XML in 21 Days

    Steven Holzner Teach Yourself XML in 21 Days THIRD EDITION 800 East 96th Street, Indianapolis, Indiana, 46240 USA Sams Teach Yourself XML in 21 Days, ASSOCIATE PUBLISHER Michael Stephens Third Edition ACQUISITIONS EDITOR Copyright © 2004 by Sams Publishing Todd Green All rights reserved. No part of this book shall be reproduced, stored in a retrieval DEVELOPMENT EDITOR system, or transmitted by any means, electronic, mechanical, photocopying, record- Songlin Qiu ing, or otherwise, without written permission from the publisher. No patent liability MANAGING EDITOR is assumed with respect to the use of the information contained herein. Although every precaution has been taken in the preparation of this book, the publisher and Charlotte Clapp author assume no responsibility for errors or omissions. Nor is any liability assumed PROJECT EDITOR for damages resulting from the use of the information contained herein. Matthew Purcell International Standard Book Number: 0-672-32576-4 INDEXER Library of Congress Catalog Card Number: 2003110401 Mandie Frank PROOFREADER Printed in the United States of America Paula Lowell First Printing: October 2003 TECHNICAL EDITOR 06050403 4321 Chris Kenyeres Trademarks TEAM COORDINATOR Cindy Teeters All terms mentioned in this book that are known to be trademarks or service marks have been appropriately capitalized. Sams Publishing cannot attest to the accuracy INTERIOR DESIGNER of this information. Use of a term in this book should not be regarded as affecting Gary Adair the validity of any trademark or service mark. COVER DESIGNER Warning and Disclaimer Gary Adair PAGE LAYOUT Every effort has been made to make this book as complete and as accurate as possi- ble, but no warranty or fitness is implied.
  • Bibliography of Erik Wilde

    Bibliography of Erik Wilde

    dretbiblio dretbiblio Erik Wilde's Bibliography References [1] AFIPS Fall Joint Computer Conference, San Francisco, California, December 1968. [2] Seventeenth IEEE Conference on Computer Communication Networks, Washington, D.C., 1978. [3] ACM SIGACT-SIGMOD Symposium on Principles of Database Systems, Los Angeles, Cal- ifornia, March 1982. ACM Press. [4] First Conference on Computer-Supported Cooperative Work, 1986. [5] 1987 ACM Conference on Hypertext, Chapel Hill, North Carolina, November 1987. ACM Press. [6] 18th IEEE International Symposium on Fault-Tolerant Computing, Tokyo, Japan, 1988. IEEE Computer Society Press. [7] Conference on Computer-Supported Cooperative Work, Portland, Oregon, 1988. ACM Press. [8] Conference on Office Information Systems, Palo Alto, California, March 1988. [9] 1989 ACM Conference on Hypertext, Pittsburgh, Pennsylvania, November 1989. ACM Press. [10] UNIX | The Legend Evolves. Summer 1990 UKUUG Conference, Buntingford, UK, 1990. UKUUG. [11] Fourth ACM Symposium on User Interface Software and Technology, Hilton Head, South Carolina, November 1991. [12] GLOBECOM'91 Conference, Phoenix, Arizona, 1991. IEEE Computer Society Press. [13] IEEE INFOCOM '91 Conference on Computer Communications, Bal Harbour, Florida, 1991. IEEE Computer Society Press. [14] IEEE International Conference on Communications, Denver, Colorado, June 1991. [15] International Workshop on CSCW, Berlin, Germany, April 1991. [16] Third ACM Conference on Hypertext, San Antonio, Texas, December 1991. ACM Press. [17] 11th Symposium on Reliable Distributed Systems, Houston, Texas, 1992. IEEE Computer Society Press. [18] 3rd Joint European Networking Conference, Innsbruck, Austria, May 1992. [19] Fourth ACM Conference on Hypertext, Milano, Italy, November 1992. ACM Press. [20] GLOBECOM'92 Conference, Orlando, Florida, December 1992. IEEE Computer Society Press. http://github.com/dret/biblio (August 29, 2018) 1 dretbiblio [21] IEEE INFOCOM '92 Conference on Computer Communications, Florence, Italy, 1992.
  • XML Parsers - a Comparative Study with Respect to Adaptability

    XML Parsers - a Comparative Study with Respect to Adaptability

    XML Parsers - A comparative study with respect to adaptability Bachelor Degree Project in Information Technology Basic level 30 ECTS Spring term 2018 Johan Holm Mats Gustavsson Supervisor: Yacine Atif Examinator: Alan Said Abstract Data migration is common as information needs to be moved and transformed between services and applications. Performance in the context of speed is important and may have a crucial impact on the handling of data. Information can be sent in varying formats and XML is one of the more commonly used. The information that is sent can change in structure from time to time and these changes needs to be handled. The parsers’ ability to handle these changes are described as the property “adaptability”. The transformation of XML files is done with the use of parsing techniques. The parsing techniques have different approaches, for example event-based or memory-based. Each approach has its pros and cons. The aim of this study is to research how three different parsers handle parsing XML documents with varying structures in the context of performance. The chosen parsing techniques are SAX, DOM and VTD. SAX uses an event-based approach while DOM and VTD uses a memory-based. Implementation of the parsers have been made with the purpose to extract information from XML documents an adding it to an ArrayList. The results from this study show that the parsers differ in performance, where DOM overall is the slowest and SAX and VTD perform somewhat equal. Although there are differences in the performance between the parsers depending on what changes are made to the XML document.
  • XML and Related Technologies Certification Prep, Part 3: XML Processing Explore How to Parse and Validate XML Documents Plus How to Use Xquery

    XML and Related Technologies Certification Prep, Part 3: XML Processing Explore How to Parse and Validate XML Documents Plus How to Use Xquery

    XML and Related Technologies certification prep, Part 3: XML processing Explore how to parse and validate XML documents plus how to use XQuery Skill Level: Intermediate Mark Lorenz ([email protected]) Senior Application Architect Hatteras Software, Inc. 26 Sep 2006 Parsing and validation represent the core of XML. Knowing how to use these capabilities well is vital to the successful introduction of XML to your project. This tutorial on XML processing teaches you how to parse and validate XML files as well as use XQuery. It is the third tutorial in a series of five tutorials that you can use to help prepare for the IBM certification Test 142, XML and Related Technologies. Section 1. Before you start In this section, you'll find out what to expect from this tutorial and how to get the most out of it. About this series This series of five tutorials helps you prepare to take the IBM certification Test 142, XML and Related Technologies, to attain the IBM Certified Solution Developer - XML and Related Technologies certification. This certification identifies an intermediate-level developer who designs and implements applications that make use of XML and related technologies such as XML Schema, Extensible Stylesheet Language Transformation (XSLT), and XPath. This developer has a strong understanding of XML fundamentals; has knowledge of XML concepts and related technologies; understands how data relates to XML, in particular with issues associated with information modeling, XML processing, XML rendering, and Web XML processing © Copyright IBM Corporation 1994, 2008. All rights reserved. Page 1 of 38 developerWorks® ibm.com/developerWorks services; has a thorough knowledge of core XML-related World Wide Web Consortium (W3C) recommendations; and is familiar with well-known, best practices.
  • Open Source Used in Cisco Unity Connection 11.5 SU 1

    Open Source Used in Cisco Unity Connection 11.5 SU 1

    Open Source Used In Cisco Unity Connection 11.5 SU 1 Cisco Systems, Inc. www.cisco.com Cisco has more than 200 offices worldwide. Addresses, phone numbers, and fax numbers are listed on the Cisco website at www.cisco.com/go/offices. Text Part Number: 78EE117C99-132949842 Open Source Used In Cisco Unity Connection 11.5 SU 1 1 This document contains licenses and notices for open source software used in this product. With respect to the free/open source software listed in this document, if you have any questions or wish to receive a copy of any source code to which you may be entitled under the applicable free/open source license(s) (such as the GNU Lesser/General Public License), please contact us at [email protected]. In your requests please include the following reference number 78EE117C99-132949842 Contents 1.1 ace 5.3.5 1.1.1 Available under license 1.2 Apache Commons Beanutils 1.6 1.2.1 Notifications 1.2.2 Available under license 1.3 Apache Derby 10.8.1.2 1.3.1 Available under license 1.4 Apache Mina 2.0.0-RC1 1.4.1 Available under license 1.5 Apache Standards Taglibs 1.1.2 1.5.1 Available under license 1.6 Apache STRUTS 1.2.4. 1.6.1 Available under license 1.7 Apache Struts 1.2.9 1.7.1 Available under license 1.8 Apache Xerces 2.6.2. 1.8.1 Notifications 1.8.2 Available under license 1.9 axis2 1.3 1.9.1 Available under license 1.10 axis2/cddl 1.3 1.10.1 Available under license 1.11 axis2/cpl 1.3 1.11.1 Available under license 1.12 BeanUtils(duplicate) 1.6.1 1.12.1 Notifications Open Source Used In Cisco Unity Connection
  • Candidate Resume

    Candidate Resume

    Flat No-a/303, Dharti Park, Behind Shriniwas , Palghar Thane MH 401501 India P : +91 9321883949 E : [email protected] W : www.hawkcl.com Hawk ID # 33574 IT / System Analyst Residential Country : India Nationality : India Resume Title : System Analyst Notice Period : 1 Days EDUCATION Qualification Institute / College /University Year Country B E / B Tech JNTU 2007 India CAREER SUMMARY From Month/ To Month/ Position Employer Country Year Year System Analyst Reputed Company 07/2010 / Software Verus Solutions 10/2007 07/2010 Developer Private Ltd ADDITIONAL CERTIFICATE AND TECHNICAL QUALIFICATION Name Of The Course Course Date Valid Upto Name Of Organisation Current Salary Expected Salary (Monthly In USD): Not Mention (Monthly In USD): Not Mention Additional Skills : Professional Summary • Eight years of experience in design, development, deployment and maintenance of enterprise web applications in ERP, Utility and Marketing domains. • Expertise in Client/ Server and application development using Java, J2ee technologies. • Experienced in leading and mentoring teams with 3-5 members. • Strong knowledge on Object Oriented Programming. • Expertise in web application development using frameworks like Struts , Spring and Hibernate. • Excellent Knowledge of MVC Architecture. • Have worked on application servers like Jboss and Tomcat. • Have worked on build and deploy tools like Ant and Maven. • Have worked on continuous integration tools like Hudson (aka Jenkins). • Have worked on consuming the SOAP web services using Apache Axis API. • Good understanding of Rest Services (RestEasy). • Working knowledge on relational databases like Oracle 10g and Postgresql 8. • Pro-active, highly motivated, results oriented and leadership skills with great team ethics. Technical Expertise • Programming Languages : Java 5/6/7.