Preface

This reference describes Oracle XML Developer's Kits (XDK) and Oracle XML DB APIs. It primarily lists the syntax of functions, methods, and procedures associated with these APIs. The Preface contains the following sections:

Audience

This guide is intended for developers building XML applications on Oracle9i database.

Organization

This document contains the following chapters:

PART I. XDK for Java Packages

This section describes Java APIs for XDK.

Chapter 1, "XML Parser for Java"

Chapter 2, "Document Object Model (DOM)"

Chapter 3, "XML Processing for Java (JAXP)"

Chapter 4, "XSLT Processing for Java"

Chapter 5, "Compression for Java"

Chapter 6, "XML Schema Processing"

Chapter 7, "XML Class Generation for Java"

Chapter 8, "XML SQL Utility for Java"

Chapter 9, "XSQL Pages Publishing Framework for Java"

Chapter 10, "Oracle XML JavaBeans"

Chapter 11, "Simple Object Access Protocol (SOAP) for Java"

Chapter 12, "TransX Utility for Java"

PART II. XDK for C Packages

This section describes C APIs for XDK.

Chapter 13, "XML Parser for C"

Chapter 14, "XSLT Processor for C"

Chapter 15, "XML Schema Processor for C"

PART III. XDK for C++ Packages

This section describes C++ APIs for XDK.

Chapter 16, "XML Parser for C++"

Chapter 17, "XSLT Processor for C++"

Chapter 18, "XML Schema Processor for C++"

Chapter 19, "XML Class Generator for C++"

PART IV. XDK for PL/SQL

This section describes PL/SQL APIs for XDK.

Chapter 20, "XML SQL Utility (XSU) for PL/SQL"

PART V. XML Database Support: Oracle XML DB for Java

This section describes Java APIs for Oracle XML DB.

Chapter 21, "Java API for XMLType"

Chapter 22, "Oracle XML DB API for Java Beans"

Chapter 23, "Resource APIs for Java/JNDI"

PART VI. XML Database Support: Oracle XML DB for PL/SQL

This section describes PL/SQL APIs for Oracle XML DB.

Chapter 24, "XMLType API for PL/SQL"

Chapter 25, "PL/SQL DOM API for XMLType"

Chapter 26, "PL/SQL Parser API for XMLType"

Chapter 27, "PL/SQL XSLT Processing for XMLType"

Chapter 28, "DBMS_XMLSCHEMA and Catalog Views for PL/SQL"

Chapter 29, "Resource Management and Access Control for PL/SQL"

Chapter 30, "Generating Queries Using DBMS_XMLGEN for PL/SQL"

Chapter 31, "Oracle XML DB Resource View API for PL/SQL"

Chapter 32, "Oracle XML DB Versioning API for PL/SQL"

Chapter 33, "Managing ConText Indexes: DBMS_XDBT in PL/SQL"

PART VII. XML Database Support: SQLX

This section describes SQL APIs for Oracle XML DB.

Chapter 34, "SQLX Functions and Operators"

PART VIII. XML Database Support: Database URI Types

This section describes URI Types APIs for Oracle XML DB.

Chapter 35, "Database URI Types"

Related Documentation

For more information, see these Oracle resources:

Many of the examples in this book use the sample schemas of the seed database, which is installed by default when you install Oracle. Refer to Oracle9i Sample Schemas for information on how these schemas were created and how you can use them yourself.

In North America, printed documentation is available for sale in the Oracle Store at

http://oraclestore.oracle.com/

Customers in Europe, the Middle East, and Africa (EMEA) can purchase documentation from

http://www.oraclebookshop.com/

Other customers can contact their Oracle representative to purchase printed documentation.

To download free release notes, installation documentation, white papers, or other collateral, please visit the Oracle Technology Network (OTN). You must register online before using OTN; registration is free and can be done at

http://otn.oracle.com/admin/account/membership.html

If you already have a username and password for OTN, then you can go directly to the documentation section of the OTN Web site at

http://otn.oracle.com/docs/index.htm

To access the database documentation search engine directly, please visit

http://tahiti.oracle.com

For additional information, see:

The Oracle XML Handbook by XML Core Development Team, Oracle. Oracle Press, 2000.
Building Oracle XML Applications by Steve Muench. O'Reilly & Associates, 2000.
XML Bible byElliotte Rusty Harold. Hungry Minds, Inc., 2001.
XML Unleashed by Morrison et al. SAMS, 1999.
Building XML Applications by St.Laurent and Cerami. McGraw-Hill Professional Publishing, 1999.
Building Web Sites with XML by Michael Floyd. Prentice Hall PTR, 1999.
Building Corporate Portals with XML by Finkelstein, Aiken and Zachman. McGraw-Hill Professional Publishing, 1999.
XML in a Nutshell by Elliotte Rusty Harold and W. Scott Means. O'Reilly & Associates, 2002.
XML in a Nutshell : A Desktop Quick Reference by Elliotte Rusty Harold and W. Scott Means. O'Reilly & Associates, 2001.
Learning XML by Erik T. Ray. O'Reilly & Associates, 2001.
XSLT by Doug Tidwell. O'Reilly & Associates, 2001.
http://www.xml.com/pub/rg/46
http://www.xml.org/xmlorg_resources/index.shtml
http://www.fawcette.com/xmlmag/
http://www.webmethods.com/
http://www.xmlwriter.com/
http://webdevelopersjournal.com/articles/why_xml.html
http://www.w3schools.com/xml/
http://www.xml101.com/examples/

Conventions

This section describes the conventions used in the text and code examples of this documentation set. It describes:

Conventions in Text

We use various conventions in text to help you more quickly identify special terms. The following table describes those conventions and provides examples of their use.

Convention	Meaning	Example
Bold	Bold typeface indicates terms that are defined in the text or terms that appear in a glossary, or both.	When you specify this clause, you create an index-organized table.
Italics	Italic typeface indicates book titles or emphasis.	Oracle9i Database Concepts Ensure that the recovery catalog and target database do not reside on the same disk.
`UPPERCASE monospace (fixed-width) font`	Uppercase monospace typeface indicates elements supplied by the system. Such elements include parameters, privileges, datatypes, RMAN keywords, SQL keywords, SQL*Plus or utility commands, packages and methods, as well as system-supplied column names, database objects and structures, usernames, and roles.	You can specify this clause only for a `NUMBER` column. You can back up the database by using the `BACKUP` command. Query the `TABLE_NAME` column in the `USER_TABLES` data dictionary view. Use the `DBMS_STATS`.`GENERATE_STATS` procedure.
`lowercase monospace (fixed-width) font`	Lowercase monospace typeface indicates executables, filenames, directory names, and sample user-supplied elements. Such elements include computer and database names, net service names, and connect identifiers, as well as user-supplied database objects and structures, column names, packages and classes, usernames and roles, program units, and parameter values. Note: Some programmatic elements use a mixture of UPPERCASE and lowercase. Enter these elements as shown.	Enter `sqlplus` to open SQL*Plus. The password is specified in the `orapwd` file. Back up the datafiles and control files in the `/disk1/oracle/dbs` directory. The `department_id`, `department_name`, and `location_id` columns are in the `hr.departments` table. Set the `QUERY_REWRITE_ENABLED` initialization parameter to `true.` Connect as `oe` user. The `JRepUtil` class implements these methods.
`lowercase italic monospace (fixed-width) font`	Lowercase italic monospace font represents placeholders or variables.	You can specify the `parallel_clause`. Run `U``old_release``.SQL` where `old_release` refers to the release you installed prior to upgrading.

Conventions in Code Examples

Code examples illustrate SQL, PL/SQL, SQL*Plus, or other command-line statements. They are displayed in a monospace (fixed-width) font and separated from normal text as shown in this example:

SELECT username FROM dba_users WHERE username = 'MIGRATE';

The following table describes typographic conventions used in code examples and provides examples of their use.

Convention	Meaning	Example
[ ]	Brackets enclose one or more optional items. Do not enter the brackets.	`DECIMAL (``digits` `[ ,` `precision` `])`
{ }	Braces enclose two or more items, one of which is required. Do not enter the braces.	`{ENABLE \| DISABLE}`
\|	A vertical bar represents a choice of two or more options within brackets or braces. Enter one of the options. Do not enter the vertical bar.	`{ENABLE \| DISABLE}` `[COMPRESS \| NOCOMPRESS]`
`...`	Horizontal ellipsis points indicate either: That we have omitted parts of the code that are not directly related to the example That you can repeat a portion of the code	`CREATE TABLE ... AS` `subquery``;` `SELECT` `col1``,` `col2``, ... ,` `coln` `FROM employees;`
. . .	Vertical ellipsis points indicate that we have omitted several lines of code not directly related to the example.
Other notation	You must enter symbols other than brackets, braces, vertical bars, and ellipsis points as shown.	`acctbal NUMBER(11,2);` `acct CONSTANT NUMBER(4) := 3;`
`Italics`	Italicized text indicates placeholders or variables for which you must supply particular values.	`CONNECT SYSTEM/``system_password` `DB_NAME =` `database_name`
`UPPERCASE`	Uppercase typeface indicates elements supplied by the system. We show these terms in uppercase in order to distinguish them from terms you define. Unless terms appear in brackets, enter them in the order and with the spelling shown. However, because these terms are not case sensitive, you can enter them in lowercase.	`SELECT last_name, employee_id FROM employees;` `SELECT * FROM USER_TABLES;` `DROP TABLE hr.employees;`
`lowercase`	Lowercase typeface indicates programmatic elements that you supply. For example, lowercase indicates names of tables, columns, or files. Note: Some programmatic elements use a mixture of UPPERCASE and lowercase. Enter these elements as shown.	`SELECT last_name, employee_id FROM employees;` `sqlplus hr/hr` `CREATE USER mjones IDENTIFIED BY ty3MU9;`

Documentation Accessibility

Our goal is to make Oracle products, services, and supporting documentation accessible, with good usability, to the disabled community. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Standards will continue to evolve over time, and Oracle Corporation is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For additional information, visit the Oracle Accessibility Program Web site at

http://www.oracle.com/accessibility/

Accessibility of Code Examples in Documentation

JAWS, a Windows screen reader, may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, JAWS may not always read a line of text that consists solely of a bracket or brace.

Accessibility of Links to External Web Sites in Documentation

This documentation may contain links to Web sites of other companies or organizations that Oracle Corporation does not own or control. Oracle Corporation neither evaluates nor makes any representations regarding the accessibility of these Web sites.