DOCSLIB.ORG

JAXP.Ps (Mpage)

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
JAXP.Ps (Mpage) 2.3 JAXP: Java API for XML Processing JAXP 1.1 How can applications use XML processors? Included in Java since JDK 1.4 – A Java -based answer: through JAXP An interface for “plugging -in ” and using XML – An overview of the JAXP interface processors in Java applications » What does it specify? – includes packages » What can be done with it? » org.xml.sax : SAX 2.0 » How do the JAXP components fit together? » org.w3c.dom: DOM Level 2 » javax.xml.parsers : [Partly based on tutorial “An Overview of the APIs ” at initialization and use of parsers http://java.sun.com/xml/jaxp/dist/1.1/docs/tutorial/overview » javax.xml.transform : /3_apis.html, from which also some graphics are borrowed] initialization and use of transformers (XSLT processors) XPT 2006 XML APIs: JAXP 1 XPT 2006 XML APIs: JAXP 2 Later Versions JAXP: XML processor plugin (1) JAXP 1.2 (2002) adds property -strings for Vendor -independent method for selecting setting the language and source of a schema processor implementation at run time used for (non -DTD -based) validation – principally through system properties JAXP 1.3 included in JDK 5.0 (2005) javax.xml.parsers.SAXParserFactory javax.xml.parsers.DocumentBuilderFactory – more flexible validation (decoupled from parsing) javax.xml.transform.TransformerFactory – support for DOM3 and XPath – Set on command line (for example, to use Apache Xerces as the DOM implementation): We'll restrict to basic ideas from JAXP 1.1 java -Djavax.xml.parsers.DocumentBuilderFactory = org.apache.xerces.jaxp.DocumentBuilderFactoryImpl XPT 2006 XML APIs: JAXP 3 XPT 2006 XML APIs: JAXP 4 JAXP: XML processor plugin (2) JAXP: Functionality −> – Set during execution ( Saxon as the XSLT impl ): Parsing using SAX 2.0 or DOM Level 2 System.setProperty ( "javax.xml.transform.TransformerFactory ", Transformation using XSLT "com.icl.saxon.TransformerFactoryImpl "); – (We ’ll study XSLT in detail later) By default, reference implementations used Adds functionality missing from SAX 2.0 and – Apache Crimson/ Xerces as the XML parser – Apache Xalan as the XSLT processor DOM Level 2: Supported by a few compliant processors: – controlling validation and handling of parse errors can – Parsers: Apache Crimson and Xerces , Aelfred , » error handling be controlled in SAX, Oracle XML Parser for Java by implementing ErrorHandler methods – XSLT transformers: Apache Xalan , Saxon – loading and saving of DOM Document objects XPT 2006 XML APIs: JAXP 5 XPT 2006 XML APIs: JAXP 6 JAXP Parsing API JAXP: Using a SAX parser (1) .newSAXParser () Included in JAXP package .getXMLReader () javax.xml.parsers Used for invoking and using SAX … Used for invoking and using SAX … XML SAXParserFactory spf = SAXParserFactory .newInstance (); .parse ( ”f.xml ”) and DOM parser implementations: f.xml DocumentBuilderFactory dbf = DocumentBuilderFactory .newInstance (); XPT 2006 XML APIs: JAXP 7 XPT 2006 XML APIs: JAXP 8 JAXP: Using a SAX parser (2) JAXP: Using a DOM parser (1) We have already seen this : .newDocumentBuilder () SAXParserFactory spf = SAXParserFactory .newInstance (); try { .newDocument () SAXParser saxParser = spf. newSAXParser (); XMLReader xmlReader = saxParser. getXMLReader (); ... .parse( ”f.xml ”) xmlReader .setContentHandler (handler ); xmlReader .parse (fileNameOrURI ); ... f.xml } catch (Exception e) { System.err.println(e.getMessage ()); System.exit(1); }; XPT 2006 XML APIs: JAXP 9 XPT 2006 XML APIs: JAXP 10 JAXP: Using a DOM parser (2) DOM building in JAXP Document Parsing a file into a DOM Document : Builder DocumentBuilderFactory dbf = (Content DocumentBuilderFactory .newInstance (); Handler ) try { // to get a new DocumentBuilder : XML Error DOM Document DocumentBuilder builder = Reader Handler dbf. newDocumentBuilder (); XML Document domDoc = (SAX DTD builder. parse (fileNameOrURI ); Parser ) Handler } catch (ParserConfigurationException e) { Entity e.printStackTrace ()); Resolver System.exit(1); }; DOM on top of SAX - So what ? XPT 2006 XML APIs: JAXP 11 XPT 2006 XML APIs: JAXP 12 JAXP: Controlling parsing (1) JAXP: Controlling parsing (2) Errors of DOM parsing can be handled – by creating a SAX ErrorHandler Further DocumentBuilderFactory » to implement error , fatalError and warning methods configuration methods to control the form of and passing it to the DocumentBuilder : the resulting DOM Document : builder. setErrorHandler (new myErrHandler ()); domDoc = builder. parse (fileName ); setIgnoringComments (true /false) Parser properties can be configured : setIgnoringElementContentWhitespace (true /false) – for both SAXParserFactories and setCoalescing (true /false) DocumentBuilderFactories (before parser /builder • combine CDATA sections with surrounding text? creation ): factory. setValidating (true /false) setExpandEntityReferences (true /false) factory. setNamespaceAware (true /false) XPT 2006 XML APIs: JAXP 13 XPT 2006 XML APIs: JAXP 14 JAXP Transformation API JAXP: Using Transformers (1) earlier known as TrAX Allows application to apply a Transformer to a .newTransformer (…) Source document to get a Result document .transform (.,.) Transformer can be created – from XSLT transformation instructions (to be discussed later ) – without instructions Source » gives an identity transformation , which simply XSLT copies the Source to the Result XPT 2006 XML APIs: JAXP 15 XPT 2006 XML APIs: JAXP 16 JAXP Transformation APIs Source -Result combinations javax.xml.transform : Source Transformer Result – Classes Transformer and TransformerFactory ; initialization similar XML Content Reader Handler to parsers and parser factories (SAX Parser ) Transformation Source object can be DOM – a DOM tree, a SAX XMLReader or an input stream DOM Output Input Output Transformation Result object can be Stream Stream – a DOM tree, a SAX ContentHandler or an output stream XPT 2006 XML APIs: JAXP 17 XPT 2006 XML APIs: JAXP 18 JAXP Transformation Packages (2) Serializing a DOM Document as XML text Classes to create Source and Result objects By an identity transformation to an output stream: from DOM, SAX and I/O streams defined in packages TransformerFactory tFactory = – javax.xml.transform.dom , TransformerFactory .newInstance (); javax.xml.transform.sax , and // Create an identity transformer : javax.xml.transform.stream Transformer transformer = tFactory. newTransformer (); Identity transformation to an output stream is a DOMSource source = new DOMSource (myDOMdoc ); vendor -neutral way to serialize DOM documents StreamResult result = (and the only option in JAXP) new StreamResult (System.out ); – “I would recommend using the JAXP interfaces until the DOM ’s own load/save module becomes available ” » Joe Kesselman , IBM & W3C DOM WG transformer. transform (source , result ); XPT 2006 XML APIs: JAXP 19 XPT 2006 XML APIs: JAXP 20 Controlling the form of the result ? Creating an XSLT Transformer We could specify the requested form of the result by Then create a tailored transfomer : an XSLT script, say, in file saveSpec.xslt : StreamSource saveSpecSrc = <xsl:transform version="1.0" new StreamSource ( xmlns:xsl="http ://www.w3.org/1999/XSL/ Transform "> new File( ”saveSpec.xslt ”) ); Transformer transformer = <xsl:output encoding="ISO -8859 -1" indent="yes " tFactory. newTransformer (saveSpecSrc ); doctype -system="reglist.dtd " /> // and use it to transform a Source to a Result , <xsl:template match ="/"> // as before <! -- copy whole document : -- > <xsl:copy -of select ="." /> </ xsl:template > The Source of transformation instructions could be </ xsl:transform > given also as a DOMSource , URL, or character reader XPT 2006 XML APIs: JAXP 21 XPT 2006 XML APIs: JAXP 22 DOM vs. Other Java/XML APIs JAXP: Summary JDOM ( www.jdom.org ), DOM4J ( www.dom4j.org ), An interface for using XML Processors JAXB ( java.sun.com /xml/ jaxb ) JAXB ( ) – SAX/DOM parsers, XSLT transformers The others may be more convenient to use, Supports pluggability of XML processors but … but … “The DOM offers not only the ability to move Defines means to control parsing, and between languages with minimal relearning, but handling of parse errors (through SAX to move between multiple implementations in ErrorHandlers ) a single language – which a specific set of classes such as JDOM can ’t support ” Defines means to write out DOM Documents » J. Kesselman , IBM & W3C DOM WG Included in Java 2 XPT 2006 XML APIs: JAXP 23 XPT 2006 XML APIs: JAXP 24.
Load more

Recommended publications
  • 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 ..................................................................
    [Show full text]
  • 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.
    [Show full text]
  • XML for Java Developers G22.3033-002 Course Roadmap
    XML for Java Developers G22.3033-002 Session 1 - Main Theme Markup Language Technologies (Part I) Dr. Jean-Claude Franchitti New York University Computer Science Department Courant Institute of Mathematical Sciences 1 Course Roadmap Consider the Spectrum of Applications Architectures Distributed vs. Decentralized Apps + Thick vs. Thin Clients J2EE for eCommerce vs. J2EE/Web Services, JXTA, etc. Learn Specific XML/Java “Patterns” Used for Data/Content Presentation, Data Exchange, and Application Configuration Cover XML/Java Technologies According to their Use in the Various Phases of the Application Development Lifecycle (i.e., Discovery, Design, Development, Deployment, Administration) e.g., Modeling, Configuration Management, Processing, Rendering, Querying, Secure Messaging, etc. Develop XML Applications as Assemblies of Reusable XML- Based Services (Applications of XML + Java Applications) 2 1 Agenda XML Generics Course Logistics, Structure and Objectives History of Meta-Markup Languages XML Applications: Markup Languages XML Information Modeling Applications XML-Based Architectures XML and Java XML Development Tools Summary Class Project Readings Assignment #1a 3 Part I Introduction 4 2 XML Generics XML means eXtensible Markup Language XML expresses the structure of information (i.e., document content) separately from its presentation XSL style sheets are used to convert documents to a presentation format that can be processed by a target presentation device (e.g., HTML in the case of legacy browsers) Need a
    [Show full text]
  • XML: Looking at the Forest Instead of the Trees Guy Lapalme Professor Département D©Informatique Et De Recherche Opérationnelle Université De Montréal
    XML: Looking at the Forest Instead of the Trees Guy Lapalme Professor Département d©informatique et de recherche opérationnelle Université de Montréal C.P. 6128, Succ. Centre-Ville Montréal, Québec Canada H3C 3J7 [email protected] http://www.iro.umontreal.ca/~lapalme/ForestInsteadOfTheTrees/ Publication date April 14, 2019 XML to PDF by RenderX XEP XSL-FO Formatter, visit us at http://www.renderx.com/ XML: Looking at the Forest Instead of the Trees Guy Lapalme Professor Département d©informatique et de recherche opérationnelle Université de Montréal C.P. 6128, Succ. Centre-Ville Montréal, Québec Canada H3C 3J7 [email protected] http://www.iro.umontreal.ca/~lapalme/ForestInsteadOfTheTrees/ Publication date April 14, 2019 Abstract This tutorial gives a high-level overview of the main principles underlying some XML technologies: DTD, XML Schema, RELAX NG, Schematron, XPath, XSL stylesheets, Formatting Objects, DOM, SAX and StAX models of processing. They are presented from the point of view of the computer scientist, without the hype too often associated with them. We do not give a detailed description but we focus on the relations between the main ideas of XML and other computer language technologies. A single compact pretty-print example is used throughout the text to illustrate the processing of an XML structure with XML technologies or with Java programs. We also show how to create an XML document by programming in Java, in Ruby, in Python, in PHP, in E4X (Ecmascript for XML) and in Swift. The source code of the example XML ®les and the programs are available either at the companion web site of this document or by clicking on the ®le name within brackets at the start of the caption of each example.
    [Show full text]
  • Testing XSLT
    Testing XSLT Tony Graham Menteith Consulting Ltd 13 Kelly's Bay Beach Skerries, Co Dublin Ireland [email protected] http://www.menteithconsulting.com Version 1.3 – XML Prague 2009 – 21 March 2009 © 2007–2009 Menteith Consulting Ltd Testing XSLT Testing XSLT Introductions 5 XSLT 5 Testing Source 5 Testing Result 6 Testing Source–Result 6 Testing the Stylesheet 7 Problem Scenarios 16 Errors That Aren't Caught By Other Tests 17 Resources 18 © 2007–2009 Menteith Consulting Ltd 3 Menteith Consulting 4 © 2007–2009 Menteith Consulting Ltd Testing XSLT Testing XSLT 1 • Introduction • Testing Source • Testing Result • Testing Source–Result • Testing the Stylesheet Introductions Who am I? 2 • Tony Graham of Menteith Consulting • XML and XSL/XSLT consultant • Based in Dublin, Ireland • Clients in Ireland, USA, France, UK • Doing XSLT since 1998 • Working with both XSLT 1.0 and XSLT 2.0 XSLT 3 Transforms source tree into result tree by associating patterns with templates XSLT / Stylesheet Source Result Tree Tree / / XSLT Processor © 2007–2009 Menteith Consulting Ltd 5 Menteith Consulting 4 Testing Source • Good if you can do it • May be well-formed or very loose schema • May be constraints that aren't easily checked 5 Testing Result • Good if you can do it • May be well-formed or very loose schema • May be constraints that aren't easily checked, e.g., XSL FO • If HTML, use HTML testing tools, e.g., WebTest • Harder to verify text output 6 Testing Source–Result 6 © 2007–2009 Menteith Consulting Ltd Testing XSLT XSLV Static Validation Tool
    [Show full text]
  • JSR-000206 Java™API for XML Processing (“Specification”)
    JSR-000206 Java™API for XML Processing (“Specification”) Version: 1.5 July 16, 2013 Maintenance Lead: Joe Wang Oracle Corporation Feedback: Please send comments to [email protected] Oracle Corporation 500 Oracle Parkway Redwood Shores, CA 94065 USA ORACLE AMERICA, INC. IS WILLING TO LICENSE THIS SPECIFICATION TO YOU ONLY UPON THE CONDITION THAT YOU ACCEPT ALL OF THE TERMS CONTAINED IN THIS AGREEMENT. PLEASE READ THE TERMS AND CONDITIONS OF THIS AGREEMENT CAREFULLY. BY DOWNLOADING THIS SPECIFICATION, YOU ACCEPT THE TERMS AND CONDITIONS OF THE AGREEMENT. IF YOU ARE NOT WILLING TO BE BOUND BY IT, SELECT THE "DECLINE" BUTTON AT THE BOTTOM OF THIS PAGE. Specification: <JSR-206 Java™API for XML Processing ("Specification") Version: 1.5 Status: Final Release Specification Lead: Oracle America, Inc. ("Specification Lead") Release: March 2013 Copyright 2013 Oracle America, Inc. All rights reserved. LIMITED LICENSE GRANTS 1. License for Evaluation Purposes. Specification Lead hereby grants you a fully-paid, non-exclusive, non- transferable, worldwide, limited license (without the right to sublicense), under Specification Lead's applicable intellectual property rights to view, download, use and reproduce the Specification only for the purpose of internal evaluation. This includes (i) developing applications intended to run on an implementation of the Specification, provided that such applications do not themselves implement any portion(s) of the Specification, and (ii) discussing the Specification with any third party; and (iii) excerpting brief portions of the Specification in oral or written communications which discuss the Specification provided that such excerpts do not in the aggregate constitute a significant portion of the Specification.
    [Show full text]
  • An Empirical Analysis of XML Parsing Using Various Operating Systems
    International Journal of Engineering and Applied Sciences (IJEAS) ISSN: 2394-3661, Volume-2, Issue-2, February 2015 An Empirical Analysis of XML parsing using various operating systems. Amitesh Saxena, Dr. Snehlata Kothari used everywhere in software. An XML Parser is a parser that Abstract— As the use of internet technologies are widely is designed to read XML and create a way for programs to use increasing, the XML markup language attains a remarkable XML. There are different types, and each has its advantages. importance due to its language neutrality and independency in Unless a program simply and blindly copies the whole using data exchange and data transfer through web XML file as a unit, every program must implement or call on environment mechanism. For improving the processing an XML parser. performance of XML parser, it is necessary to find out a mechanism, in which we get minimum processing time while B. DOM (Document Object Model) parsing of XML documents. In this paper, XML documents are being experimentally It supports navigating and modifying XML documents tested using various operating systems to determine, whether an - Hierarchical tree representation of document operating system effect the processing time of XML parsing. - Tree follows standard API - Creating tree is vendor specific Index Terms— XML Parser, DOM Parser, Operating DOM is a language-neutral specification system. - Binding exist for Java, C++, CORBA, JavaScript, C# - can switch to other language. I. INTRODUCTION The Document Object Model (DOM) is In Present world, mega information are sharing and an interface-oriented application programming interface that transmitting, In this XML plays a very significant role as a allows for navigation of the entire document as if it were a tree worldwide design for data interchange.
    [Show full text]
  • Xquery 3.0 69 Higher-Order Functions 75 Full-Text 82 Full-Text/Japanese 85 Xquery Update 87 Java Bindings 91 Packaging 92 Xquery Errors 95 Serialization 105
    BaseX Documentation Version 7.2 PDF generated using the open source mwlib toolkit. See http://code.pediapress.com/ for more information. PDF generated at: Sat, 24 Mar 2012 17:30:37 UTC Contents Articles Main Page 1 Getting Started 3 Getting Started 3 Startup 4 Startup Options 6 Start Scripts 13 User Interfaces 16 Graphical User Interface 16 Shortcuts 20 Database Server 23 Standalone Mode 26 Web Application 27 General Info 30 Databases 30 Binary Data 32 Parsers 33 Commands 37 Options 50 Integration 64 Integrating oXygen 64 Integrating Eclipse 66 Query Features 68 Querying 68 XQuery 3.0 69 Higher-Order Functions 75 Full-Text 82 Full-Text/Japanese 85 XQuery Update 87 Java Bindings 91 Packaging 92 XQuery Errors 95 Serialization 105 XQuery Modules 108 Cryptographic Module 108 Database Module 113 File Module 120 Full-Text Module 125 HTTP Module 128 Higher-Order Functions Module 131 Index Module 133 JSON Module 135 Map Module 140 Math Module 144 Repository Module 148 SQL Module 149 Utility Module 153 XSLT Module 157 ZIP Module 160 ZIP Module: Word Documents 162 Developing 164 Developing 164 Integrate 165 Git 166 Maven 172 Releases 174 Translations 175 HTTP Services 176 REST 176 REST: POST Schema 184 RESTXQ 185 WebDAV 189 WebDAV: Windows 7 190 WebDAV: Windows XP 192 WebDAV: Mac OSX 195 WebDAV: GNOME 197 WebDAV: KDE 199 Client APIs 201 Clients 201 Standard Mode 202 Query Mode 203 PHP Example 205 Server Protocol 206 Server Protocol: Types 210 Java Examples 212 Advanced User's Guide 214 Advanced User's Guide 214 Configuration 215 Catalog Resolver 216 Statistics 218 Backups 222 User Management 222 Transaction Management 224 Logging 225 Events 226 Indexes 228 Execution Plan 230 References Article Sources and Contributors 231 Image Sources, Licenses and Contributors 233 Article Licenses License 234 Main Page 1 Main Page Welcome to the documentation of BaseX! BaseX [1] is both a light-weight, high-performance and scalable XML Database and an XPath/XQuery Processor with full support for the W3C Update and Full Text extensions.
    [Show full text]
  • Java API for XML Processing (JAXP)
    Java API for XML Processing (JAXP) • API that provides an abstraction layer to XML parser implementations (specifically implementations of DOM and SAX), and applications that process Extensible Stylesheet Language Transformations (XSLT) • JAXP is is a layer above the parser APIs that makes it easier to perform some vendor-specific tasks in a vendor-neutral fashion. JAXP employs the Abstract Factory design pattern to provide a plugability layer, which allows you to plug in an implementation of DOM or SAX, or an application that processes XSLT • The primary classes of the JAXP plugability layer are javax.xml.parsers.DocumentBuilderFactory, javax.xml.parsers.SAXParserFactory, and javax.xml.transform.TransformerFactory. • Classes are abstract so you must ask the specific factory to create an instance of itself, and then use that instance to create a javax.xml.parsers.DocumentBuilder, javax.xml.parsers.SAXParser, or javax.xml.transform.Transformer, respectively. • DocumentBuilder abstracts the underlying DOM parser implementation, SAXParser the SAX parser implementation, and Transformer the underlying XSLT processor. DocumentBuilder, SAXParser, and Transformer are also abstract classes, so instances of them can only be obtained through their respective factory. JAXP Example - 1 import java.io.*; import javax.xml.*; import org.w3c.dom.Document; import org.xml.sax.SAXException; import javawebbook.sax.ContentHandlerExample; public class JAXPTest { public static void main(String[] args) throws Exception { File xmlFile = new File(args[0]); File
    [Show full text]
  • 1 Agenda Summary of Previous Session
    XML for Java Developers G22.3033-002 Session 7 - Main Theme XML Information Rendering (Part I) Dr. Jean-Claude Franchitti New York University Computer Science Department Courant Institute of Mathematical Sciences 1 Agenda n Summary of Previous Session n Extensible Stylesheet Language Transformation (XSL-T) n Extensible Stylesheet Language Formatting Object (XSL-FO) n XML and Document/Content Management n Assignment 4a+4b (due in two week) 2 Summary of Previous Session n Advanced XML Parser Technology n JDOM: Java-Centric API for XML n JAXP: Java API for XML Processing n Parsers comparison n Latest W3C APIs and Standards for Processing XML n XML Infoset, DOM Level 3, Canonical XML n XML Signatures, XBase, XInclude n XML Schema Adjuncts n Java-Based XML Data Processing Frameworks n Assignment 3a+3b (due next week) 3 1 XML-Based Rendering Development n XML Software Development Methodology n Language + Stepwise Process + Tools n Rational Unified Process (RUP) v.s. “XML Unified Process” n XML Application Development Infrastructure n Metadata Management (e.g., XMI) n XSLT, XPath XSL -FO APIs (JAXP, JAXB, JDOM, SAX, DOM) n XML Tools (e.g., XML Editors,Apache’s FOP, Antenna House’s XSL Formatter, HTML/CSS1/2/3, XHTML, XForms, WCAG n XML Applications Involved in the Rendering Phase: n Application(s) of XML n XML-based applications/services (markup language mediators) n MOM, POP, Other Services (e.g., persistence) 4 n Application Infrastructure Frameworks What is XSL? n XSL is a language for expressing stylesheets. It consists of two parts: n A language for transforming XML documents n A XML vocabulary for specifying formatting semantics n See http://www.w3.org/Style/XSL for the XSLT 1.0/XPath 1.0 Recs, the XSL-FO 1.0 candidate rec, and working drafts of XSLT 1.1/2.0 and XPath 2.0 n A XSL stylesheet specifies the presentation of a class of XML documents.
    [Show full text]
  • Xquery API for Java™ (XQJ) 1.0 Specification Version 0.9 (JSR 225 Public Draft Specification) May 21, 2007
    XQuery API for Java™ (XQJ) 1.0 Specification Version 0.9 (JSR 225 Public Draft Specification) May 21, 2007 Spec Lead: Jim Melton Oracle Editor: Marc Van Cappellen DataDirect Technologies This document is the Public Draft Specification of the XQuery API for Java™ (XQJ) 1.0. It describes the current state of the XQuery API for Java™ (XQJ), and is subject to possibly changes and should not be considered to be in any way final. Comments on this specification should be sent to [email protected]. Copyright © 2003, 2006, 2007, Oracle. All rights reserved. Java™ is a registered trademark of Sun Microsystems, Inc. http://www.sun.com JSR 225 Public Draft Specification – Version 0.9 SPECIFICATION LICENSE Oracle USA (the “Spec Lead”) for the XQuery API for Java specification (the “Specification”) hereby grant a perpetual, non-exclusive, worldwide, fully paid-up, royalty-free, irrevocable (except as explicitly set forth below) license to copy and display the Specification, in any medium without fee or royalty, provided that you include the following on ALL copies, or portions thereof, that you make: 1. A link or URL to the Specification at this location: __________. 2. The copyright notice as shown herein. In addition, to the extent that an implementation of the Specification would be considered a derivative work under applicable law requiring a license grant from the holder of the copyright in the Specification, the Spec Lead grants a copyright license solely for the purpose of making and/or distributing an implementation of the Specification that: (a) except for the RI code licensed from Oracle under the RI License, does not include or otherwise make any use of the RI; (b) fully implements the Specification including all of its required interfaces and functionality; (c) does not modify, subset, superset or otherwise extend those public class or interface declarations whose names begin with “java;” and (d) passes the TCK.
    [Show full text]
  • XML and Java XML Parsing Program for Today Extensible Markup
    11/8/10 Program for today • Introduc?on to XML • Parsing XML XML and Java XML Parsing • Wri?ng XML ICW 2010 Lecture 11 Marco Cova Internet Compu?ng Workshop 2 Extensible Markup Language (XML) Extensible Markup Language (XML) • We know how to store data on the server • How can we send todo – Rela?on database, SQL, and JDBC items from users to • We know how to present data to users server? – HTML, CSS, and JavaScript Alice’s todos – Plain text? • We know how to send data over the network – HTML? – Sockets • It would be easy if we had – HTTP tags to describe the items • We’ll see how you can handle user requests and send back Bob’s todos Todo server we exchange (todos, in appropriate responses over HTTP this case) – Servlets and JSP (next on!) • XML allows to do that • What if data has to be processed by another soUware – Feeds: RSS, ATOM instead of being displayed to a human user? – RPC: SOAP Charlie’s todos Marco Cova Internet Compu?ng Workshop 3 Marco Cova Internet Compu?ng Workshop 4 Example: RSS Well-formed, valid XML <?xml version="1.0" encoding="UTF-8"?> • Well-formed document <rss version="2.0”> <channel> – Starts with prolog, e.g., <?tle> &#187; School News</?tle> <?xml version="1.0" encoding="UTF-8”?> <link>hkp://www.cs.bham.ac.uk/sys/news/content</link> <descripon>School of Computer Science, The University of Birmingham</descripon> – Has one root element, e.g., <pubDate>Tue, 21 Sep 2010 12:08:34 +0000</pubDate> <rss version="2.0”> <generator>hkp://wordpress.org/?v=2.7.1</generator> – <language>en</language> Elements nest properly
    [Show full text]