Contents
- Audience
- Documentation Accessibility
- Related Documents
- Conventions
- Features Introduced in Oracle XML Developer's Kit 10g Release 2 (10.2)
- Features Introduced in Oracle XML Developer's Kit 10g Release 1 (10.1)
- Overview of Oracle XML Developer's Kit (XDK)
- XDK Components
-
- XML Parsers
- XSLT Processors
- XML Schema Processors
- XML Class Generators
- XML Pipeline Processor
- XDK JavaBeans
- Oracle XML SQL Utility (XSU)
-
- Handling or Representing an XML Document
- Using XSU with an XML Class Generator
- TransX Utility
- XSQL Pages Publishing Framework
- Soap Services
- XSLT Virtual Machine (XVM)
- XML Document Generation with the XDK Components
-
- XML Document Generation with Java
- XML Document Generation with C
- XML Document Generation with C++
- Development Tools and Frameworks for the XDK
-
- Oracle JDeveloper
- User Interface XML (UIX)
- Oracle Reports
- Oracle XML Gateway
- Oracle Data Provider for .NET
- Installing the XDK
- Installing Java XDK Components
- Java XDK Component Dependencies
- Setting Up the Java XDK Environment
-
- Setting Java XDK Environment Variables for UNIX
-
- Testing the Java XDK Environment on UNIX
- Setting Java XDK Environment Variables for Windows
-
- Testing the Java XDK Environment on Windows
- Verifying the Java XDK Components Version
- Introduction to the XML Parser for Java
-
- Prerequisites
- Standards and Specifications
- DOM, SAX, and JAXP in the XML Parser
-
- DOM in the XML Parser
- SAX in the XML Parser
- JAXP in the XML Parser
- Namespace Support in the XML Parser
- Validation in the XML Parser
- Compression in the XML Parser
- Using the XML Parser for Java: Overview
-
- Using the XML Parser for Java: Basic Process
- Running the XML Parser Demo Programs
- Using the XML Parser Command-Line Utility
- Parsing XML with DOM
-
- Using the DOM API
- Performing Basic DOM Parsing
- Performing DOM Operations with Namespaces
- Performing DOM Operations with Events
- Performing DOM Operations with Ranges
- Performing DOM Operations with TreeWalker
- Parsing XML with SAX
-
- Using the SAX API
- Performing Basic SAX Parsing
- Performing Basic SAX Parsing with Namespaces
- Performing SAX Parsing with XMLTokenizer
- Parsing XML with JAXP
-
- Using the JAXP API
-
- Using the SAX API Through JAXP
- Using the DOM API Through JAXP
- Transforming XML Through JAXP
- Parsing with JAXP
- Performing Basic Transformations with JAXP
- Compressing XML
-
- Compressing and Decompressing XML from DOM
-
- Compressing a DOM Object
- Decompressing a DOM Object
- Compressing and Decompressing XML from SAX
-
- Compressing a SAX Object
- Decompressing a SAX Object
- Tips and Techniques for Parsing XML
-
- Extracting Node Values from a DOM Tree
- Merging Documents with appendChild()
- Parsing DTDs
-
- Loading External DTDs
- Caching DTDs with setDoctype
- Handling Character Sets with the XML Parser
-
- Detecting the Encoding of an XML File on the Operating System
- Detecting the Encoding of XML Stored in an NCLOB Column
- Writing an XML File in a Nondefault Encoding
- Working with XML in Strings
- Parsing XML Documents with Accented Characters
- Handling Special Characters in Tag Names
- Introduction to the XSLT Processor
-
- Prerequisites
- Standards and Specifications
- XML Transformation with XSLT 1.0 and 2.0
- Using the XSLT Processor for Java: Overview
-
- Using the XSLT Processor: Basic Process
- Running the XSLT Processor Demo Programs
- Using the XSLT Processor Command-Line Utility
-
- Using the XSLT Processor Command-Line Utility: Example
- Transforming XML
-
- Performing Basic XSL Transformation
- Obtaining DOM Results from an XSL Transformation
- Programming with Oracle XSLT Extensions
-
- Overview of Oracle XSLT Extensions
- Specifying Namespaces for XSLT Extension Functions
- Using Static and Non-Static Java Methods in XSLT
- Using Constructor Extension Functions
- Using Return Value Extension Functions
- Tips and Techniques for Transforming XML
-
- Merging XML Documents with XSLT
- Creating an HTML Input Form Based on the Columns in a Table
- Introduction to XML Validation
-
- Prerequisites
- Standards and Specifications
- XML Validation with DTDs
-
- DTD Samples in the XDK
- XML Validation with XML Schemas
-
- XML Schema Samples in the XDK
- Differences Between XML Schemas and DTDs
- Using the XML Schema Processor: Overview
-
- Using the XML Schema Processor: Basic Process
- Running the XML Schema Processor Demo Programs
- Using the XML Schema Processor Command-Line Utility
-
- Using oraxml to Validate Against a Schema
- Using oraxml to Validate Against a DTD
- Validating XML with XML Schemas
-
- Validating Against Internally Referenced XML Schemas
- Validating Against Externally Referenced XML Schemas
- Validating a Subsection of an XML Document
- Validating XML from a SAX Stream
- Validating XML from a DOM
- Validating XML from Designed Types and Elements
- Validating XML with the XSDValidator Bean
- Tips and Techniques for Programming with XML Schemas
-
- Overriding the Schema Location with an Entity Resolver
- Converting DTDs to XML Schemas
- Introduction to the JAXB Class Generator
-
- Prerequisites
- Standards and Specifications
- JAXB Class Generator Features
- Marshalling and Unmarshalling with JAXB
- Validation with JAXB
- JAXB Customization
- Using the JAXB Class Generator: Overview
-
- Using the JAXB Processor: Basic Process
- Running the XML Schema Processor Demo Programs
- Using the JAXB Class Generator Command-Line Utility
-
- Using the JAXB Class Generator Command-Line Utility: Example
- JAXB Features Not Supported in the XDK
- Processing XML with the JAXB Class Generator
-
- Binding Complex Types
-
- Defining the Schema
- Generating and Compiling the Java Classes
- Processing the XML Data
- Customizing a Class Name in a Top-Level Element
-
- Defining the Schema
- Generating and Compiling the Java Classes
- Processing the XML Data
- Introduction to the XML Pipeline Processor
-
- Prerequisites
- Standards and Specifications
- Multistage XML Processing
- Customized Pipeline Processes
- Using the XML Pipeline Processor: Overview
-
- Using the XML Pipeline Processor: Basic Process
- Running the XML Pipeline Processor Demo Programs
- Using the XML Pipeline Processor Command-Line Utility
- Processing XML in a Pipeline
-
- Creating a Pipeline Document
-
- Example of a Pipeline Document
- Writing a Pipeline Processor Application
- Writing a Pipeline Error Handler
- Introduction to XDK JavaBeans
-
- Prerequisites
- Standards and Specifications
- XDK JavaBeans Features
-
- DOMBuilder
- XSLTransformer
- DBAccess
- XMLDBAccess
- XMLDiff
- XMLCompress
- XSDValidator
- Using the XDK JavaBeans: Overview
-
- Using the XDK JavaBeans: Basic Process
-
- Using the DOMBuilder JavaBean: Basic Process
- Using the XSLTransformer JavaBean: Basic Process
- Using the XMLDBAccess JavaBean: Basic Process
- Using the XMLDiff JavaBean: Basic Process
- Running the JavaBean Demo Programs
-
- Running sample1
- Running sample2
- Running sample3
- Running sample4
- Running sample5
- Running sample6
- Running sample7
- Running sample8
- Running sample9
- Running sample10
- Processing XML with the XDK JavaBeans
-
- Processing XML Asynchronously with the DOMBuilder and XSLTransformer Beans
-
- Parsing the Input XSLT Stylesheet
- Processing the XML Documents Asynchronously
- Comparing XML Documents with the XMLDiff Bean
-
- Comparing the XML Files and Generating a Stylesheet
- Introduction to the XML SQL Utility (XSU)
-
- Prerequisites
- XSU Features
- XSU Restrictions
- Using the XML SQL Utility: Overview
-
- Using XSU: Basic Process
-
- Generating XML with the XSU Java API: Basic Process
- Performing DML with the XSU Java API: Basic Process
- Generating XML with the XSU PL/SQL API: Basic Process
- Performing DML with the PL/SQL API: Basic Process
- Installing XSU
-
- Installing XSU in the Database
- Installing XSU in an Application Server
- Installing XSU in a Web Server
- Running the XSU Demo Programs
- Using the XSU Command-Line Utility
-
- Generating XML with the XSU Command-Line Utility
- Generating XMLType Data with the XSU Command-Line Utility
- Performing DML with the XSU Command-Line Utility
- Programming with the XSU Java API
-
- Generating a String with OracleXMLQuery
-
- Running the testXMLSQL Program
- Generating a DOM Tree with OracleXMLQuery
- Paginating Results with OracleXMLQuery
-
- Limiting the Number of Rows in the Result Set
- Keeping the Object Open for the Duration of the User's Session
- Paginating Results with OracleXMLQuery: Example
- Generating Scrollable Result Sets
- Generating XML from Cursor Objects
- Inserting Rows with OracleXMLSave
-
- Inserting XML into All Columns with OracleXMLSave
- Inserting XML into a Subset of Columns with OracleXMLSave
- Updating Rows with OracleXMLSave
-
- Updating with Key Columns with OracleXMLSave
- Updating a Column List with OracleXMLSave
- Deleting Rows with OracleXMLSave
-
- Deleting by Row with OracleXMLSave
- Deleting by Key with OracleXMLSave
- Handling XSU Java Exceptions
-
- Obtaining the Parent Exception
- Raising a No Rows Exception
- Programming with the XSU PL/SQL API
-
- Generating XML from Simple Queries with DBMS_XMLQuery
- Specifying Element Names with DBMS_XMLQuery
- Paginating Results with DBMS_XMLQuery
- Setting Stylesheets in XSU
- Binding Values in XSU
- Inserting XML with DBMS_XMLSave
-
- Inserting Values into All Columns with DBMS_XMLSave
- Inserting into a Subset of Columns with DBMS_XMLSave
- Updating with DBMS_XMLSave
-
- Updating with Key Columns with DBMS_XMLSave
- Specifying a List of Columns with DBMS_XMLSave: Example
- Deleting with DBMS_XMLSave
-
- Deleting by Row with DBMS_XMLSave: Example
- Deleting by Key with DBMS_XMLSave: Example
- Handling Exceptions in the XSU PL/SQL API
- Reusing the Context Handle with DBMS_XMLSave
- Tips and Techniques for Programming with XSU
-
- How XSU Maps Between SQL and XML
-
- Default SQL to XML Mapping
- Default XML to SQL Mapping
- Customizing Generated XML
- How XSU Processes SQL Statements
-
- How XSU Queries the Database
- How XSU Inserts Rows
- How XSU Updates Rows
- How XSU Deletes Rows
- How XSU Commits After DML
- Introduction to the TransX Utility
-
- Prerequisites
- TransX utility Features
-
- Simplified Multilingual Data Loading
- Simplified Data Format Support and Interface
- Additional TransX utility Features
- Using the TransX Utility: Overview
-
- Using the TransX Utility: Basic Process
- Running the TransX Utility Demo Programs
- Using the TransX Command-Line Utility
-
- TransX utility Command-Line Options
- TransX Utility Command-Line Parameters
- Loading Data with the TransX Utility
-
- Storing Messages in the Database
- Creating a Dataset in a Predefined Format
-
- Format of the Input XML Document
- Specifying Translations in a Dataset
- Loading the Data
- Querying the Data
- Introduction to the XSQL Pages Publishing Framework
-
- Prerequisites
- Using the XSQL Pages Publishing Framework: Overview
-
- Using the XSQL Pages Framework: Basic Process
- Setting Up the XSQL Pages Framework
-
- Creating and Testing XSQL Pages with Oracle JDeveloper
- Setting the CLASSPATH for XSQL Pages
- Configuring the XSQL Servlet Container
- Setting Up the Connection Definitions
- Running the XSQL Pages Demo Programs
-
- Setting Up the XSQL Demos
- Running the XSQL Demos
- Using the XSQL Pages Command-Line Utility
- Generating and Transforming XML with XSQL Servlet
-
- Composing XSQL Pages
-
- Using Bind Parameters
- Using Lexical Substitution Parameters
- Providing Default Values for Bind and Substitution Parameters
- How the XSQL Page Processor Handles Different Types of Parameters
- Producing Datagrams from SQL Queries
- Transforming XML Datagrams into an Alternative XML Format
- Transforming XML Datagrams into HTML for Display
- Using XSQL in Java Programs
- XSQL Pages Tips and Techniques
-
- XSQL Pages Limitations
- Hints for Using the XSQL Servlet
-
- Specifying a DTD While Transforming XSQL Output to a WML Document
- Testing Conditions in XSQL Pages
- Passing a Query Result to the WHERE Clause of Another Query
- Handling Multi-Valued HTML Form Parameters
- Invoking PL/SQL Wrapper Procedures to Generate XML Datagrams
- Accessing Contents of Posted XML
- Changing Database Connections Dynamically
- Retrieving the Name of the Current XSQL Page
- Resolving Common XSQL Connection Errors
-
- Receiving "Unable to Connect" Errors
- Receiving "No Posted Document to Process" When Using HTTP POST
- Security Considerations for XSQL Pages
-
- Installing Your XSQL Configuration File in a Safe Directory
- Disabling Default Client Stylesheet Overrides
- Protecting Against the Misuse of Substitution Parameters
- Customizing the XSQL Configuration File Name
- Controlling How Stylesheets Are Processed
-
- Overriding Client Stylesheets
- Controlling the Content Type of the Returned Document
- Assigning the Stylesheet Dynamically
- Processing XSLT Stylesheets in the Client
- Providing Multiple Stylesheets
- Working with Array-Valued Parameters
-
- Supplying Values for Array-Valued Parameters
- Setting Array-Valued Page or Session Parameters from Strings
- Binding Array-Valued Parameters in SQL and PL/SQL Statements
- Setting Error Parameters on Built-in Actions
-
- Using Conditional Logic with Error Parameters
- Formatting XSQL Action Handler Errors
- Including XMLType Query Results in XSQL Pages
- Handling Posted XML Content
-
- Understanding XML Posting Options
- Producing PDF Output with the FOP Serializer
- Performing XSQL Customizations
-
- Writing Custom XSQL Action Handlers
-
- Implementing the XSQLActionHandler Interface
- Using Multivalued Parameters in Custom XSQL Actions
- Implementing Custom XSQL Serializers
-
- Techniques for Using a Custom Serializer
- Assigning a Short Name to a Custom Serializer
- Using a Custom XSQL Connection Manager for JDBC Datasources
- Writing Custom XSQL Connection Managers
-
- Accessing Authentication Information in a Custom Connection Manager
- Implementing a Custom XSQLErrorHandler
- Providing a Custom XSQL Logger Implementation
- Introduction to SOAP
-
- Prerequisites
- Standards and Specifications
- Using SOAP and the Java XDK: Overview
-
- Subpackages in oracle.soap
- Subpackages in org.apache.soap
- Developing SOAP Applications with the Java XDK
-
- Using SOAP Providers
- Using SOAP Transports
- Using SOAP Handlers
- Using the SOAP Request Handler
- Tips and Techniques for Using SOAP with the Java XDK
-
- Oracle Database SOAP and IDAP
- Oracle Database SOAP Security Features
- Installing C XDK Components
- Configuring the UNIX Environment for C XDK Components
-
- C XDK Component Dependencies on UNIX
- Setting C XDK Environment Variables on UNIX
- Testing the C XDK Runtime Environment on UNIX
- Setting Up and Testing the C XDK Compile-Time Environment on UNIX
-
- Testing the C XDK Compile-Time Environment on UNIX
- Verifying the C XDK Component Version on UNIX
- Configuring the Windows Environment for C XDK Components
-
- C XDK Component Dependencies on Windows
- Setting C XDK Environment Variables on Windows
- Testing the C XDK Runtime Environment on Windows
- Setting Up and Testing the C XDK Compile-Time Environment on Windows
-
- Testing the C XDK Compile-Time Environment on Windows
- Using the C XDK Components with Visual C/C++ on Windows
-
- Setting a Path for a Project in Visual C/C++ on Windows
- Setting the Library Path in Visual C/C++ on Windows
- Overview of the Unified C API
- Globalization Support for the C XDK Components
- Introduction to the XML Parser for C
-
- Prerequisites
- Standards and Specifications
- Using the XML Parser for C
-
- Overview of the Parser API for C
-
- XML Parser for C Datatypes
- XML Parser for C Defaults
- Using the XML Parser for C: Basic Process
- Running the XML Parser for C Demo Programs
- Using the C XML Parser Command-Line Utility
-
- Using the XML Parser Command-Line Utility: Example
- Using the DOM API for C
-
- Creating the Top-Level Context
- Controlling the Data Encoding of XML Documents for the C API
- Using NULL-Terminated and Length-Encoded C API Functions
- Handling Errors with the C API
- Using the SAX API for C
- Using OCI and the XDK C API
-
- Using XMLType Functions and Descriptions
- Initializing an XML Context
- Creating XMLType Instances on the Client
- Operating on XML Data in the Database Server
- Using OCI and the XDK C API: Examples
- XVM Processor
-
- XVM Usage Example
- Using the XVM Processor Command-Line Utility
- Accessing XVM Processor for C
- XSLT processor
-
- XSLT Processor Usage Example
- XPath Processor Usage Example
- Using the C XSLT Processor Command-Line Utility
- Accessing Oracle XSLT processor for C
- Using the Demo Files Included with the Software
-
- Building the C Demo Programs for XSLT
- Oracle XML Schema Processor for C
-
- Oracle XML Schema for C Features
- Standards Conformance
- XML Schema Processor for C: Supplied Software
- Using the C XML Schema Processor Command-Line Utility
- XML Schema Processor for C Usage Diagram
- How to Run XML Schema for C Sample Programs
- Introduction to SOAP for C
-
- SOAP Messaging Overview
-
- SOAP Message Format
- Using SOAP Clients
- Using SOAP Servers
- SOAP C Functions
- SOAP Example 1: Sending an XML Document
- SOAP Example 2: A Response Asking for Clarification
- SOAP Example 3: Using POST
- Installing the C++ XDK Components
- Configuring the UNIX Environment for C++ XDK Components
-
- C++ XDK Component Dependencies on UNIX
- Setting C++ XDK Environment Variables on UNIX
- Testing the C++ XDK Runtime Environment on UNIX
- Setting Up and Testing the C++ XDK Compile-Time Environment on UNIX
-
- Testing the C++ XDK Compile-Time Environment on UNIX
- Verifying the C++ XDK Component Version on UNIX
- Configuring the Windows Environment for C++ XDK Components
-
- C++ XDK Component Dependencies on Windows
- Setting C++ XDK Environment Variables on Windows
- Testing the C++ XDK Runtime Environment on Windows
- Setting Up and Testing the C++ XDK Compile-Time Environment on Windows
-
- Testing the C++ XDK Compile-Time Environment on Windows
- Using the C++ XDK Components with Visual C/C++
- What is the Unified C++ API?
- Accessing the C++ Interface
- OracleXML Namespace
-
- OracleXML Interfaces
- Ctx Namespace
-
- OracleXML Datatypes
- Ctx Interfaces
- IO Namespace
-
- IO Datatypes
- IO Interfaces
- Tools Package
-
- Tools Interfaces
- Error Message Files
- Introduction to Parser for C++
- DOM Namespace
-
- DOM Datatypes
- DOM Interfaces
- DOM Traversal and Range Datatypes
- DOM Traversal and Range Interfaces
- Parser Namespace
-
- GParser Interface
- DOMParser Interface
- SAXParser Interface
-
- SAX Event Handlers
- Thread Safety
- XML Parser for C++ Usage
- XML Parser for C++ Default Behavior
- C++ Sample Files
- Accessing XSLT for C++
- Xsl Namespace
-
- Xsl Interfaces
- XSLT for C++ DOM Interface Usage
- Invoking XSLT for C++
-
- Command Line Usage
- Writing C++ Code to Use Supplied APIs
- Using the Sample Files Included with the Software
- Oracle XML Schema Processor for C++
-
- Oracle XML Schema for C++ Features
-
- Online Documentation
- Standards Conformance
- XML Schema Processor API
-
- Invoking XML Schema Processor for C++
- Running the Provided XML Schema for C++ Sample Programs
- XPath Interfaces
- Sample Programs
- Accessing XML C++ Class Generator
- Using XML C++ Class Generator
-
- External DTD Parsing
- Error Message Files
- Using the XML C++ Class Generator Command-Line Utility
-
- Input to the XML C++ Class Generator
- Using the XML C++ Class Generator Examples
-
- XML C++ Class Generator Example 1: XML — Input File to Class Generator, CG.xml
- XML C++ Class Generator Example 2: DTD — Input File to Class Generator, CG.dtd
- XML C++ Class Generator Example 3: CG Sample Program
- XSQL Configuration File Parameters
- <xsql:action>
- <xsql:delete-request>
- <xsql:dml>
- <xsql:if-param>
- <xsql:include-owa>
- <xsql:include-param>
- <xsql:include-posted-xml>
- <xsql:include-request-params>
- <xsql:include-xml>
- <xsql:include-xsql>
- <xsql:insert-param>
- <xsql:insert-request>
- <xsql:query>
- <xsql:ref-cursor-function>
- <xsql:set-cookie>
- <xsql:set-page-param>
- <xsql:set-session-param>
- <xsql:set-stylesheet-param>
- <xsql:update-request>
- Introduction to DLF
-
- Naming Conventions for DLF
-
- Elements and Attributes
- Values
- File Extensions
- General Structure of DLF
-
- Tree Structure of DLF
- DLF Specifications
-
- XML Declaration in DLF
- Entity References in DLF
- Elements in DLF
-
- Top Level Table Element
- Translation Elements
- Lookup Key Elements
- Metadata Elements
- Data Elements
- Attributes in DLF
-
- DLF Attributes
- XML Namespace Attributes
- DLF Examples
-
- Minimal DLF Document
- Typical DLF Document
- Localized DLF Document
- DLF References
- XML Standards Supported by the XDK
-
- Summary of XML Standards Supported by the XDK
- XML Standards for the XDK for Java
-
- DOM Standard for the XDK for Java
- XSLT Standard for the XDK for Java
- JAXB Standard for the XDK for Java
- Pipeline Definition Language Standard for the XDK for Java
- Character Sets Supported by the XDK
-
- Character Sets Supported by the XDK for Java
- Character Sets Supported by the XDK for C
- XML Error Messages
-
- XML Parser Error Messages
-
- XML-20003: missing token string at line string, column string
- XML-20004: missing keyword string at line string, column string
- XML-20005: missing keyword string or string at line string, column string
- XML-20006: unexpected text at line string, column string; expected EOF
- XML-20007: missing content model in element declaration at line string, column string
- XML-20008: missing element name in content model at line string, column string
- XML-20009: target name string of processing instruction at line string, column string is reserved
- XML-20010: missing notation name in unparsed entity declaration at line string, column string
- XML-20011: missing attribute type in attribute-list declaration at line string, column string
- XML-20012: missing white space at line string, column string
- XML-20013: invalid character string in entity value at line string, column string
- XML-20014: -- not allowed in comment at line string, column string
- XML-20015: ]]> not allowed in text at line string, column string
- XML-20016: white space not allowed before occurrence indicator at line string, column string
- XML-20017: occurrence indicator string not allowed in mixed-content at line string, column string
- XML-20018: content list not allowed inside mixed-content at line string, column string
- XML-20019: duplicate element string in mixed-content declaration at line string, column string
- XML-20020: root element string does not match the DOCTYPE name string at line string, column string
- XML-20021: duplicate element declaration string at line string, column string
- XML-20022: element string has multiple ID attributes at line string, column string
- XML-20023: ID attribute string in element string must be #IMPLIED or #REQUIRED at line string, column string
- XML-20024: missing required attribute string in element string at line string, column string
- XML-20025: duplicate ID value: string
- XML-20026: undefined ID value string in IDREF
- XML-20027: attribute string in element string has invalid enumeration value string at line string, column string
- XML-20028: attribute string in element string has invalid value string, must be string at line string, column {5}
- XML-20029: attribute default must be REQUIRED, IMPLIED, or FIXED at line string, column string
- XML-20030: invalid text in content of element string at line string, column string
- XML-20031: invalid element string in content of element string at line string, column string
- XML-20032: incomplete content in element string at line string, column string
- XML-20033: invalid replacement-text for entity string at line string, column string
- XML-20034: end-element tag string does not match start-element tag string at line string, column string
- XML-20035: duplicate attribute string in element string at line string, column string
- XML-20036: invalid character string in attribute value at line string, column string
- XML-20037: invalid reference to external entity string in attribute string at line string, column string
- XML-20038: invalid reference to unparsed entity string in element string at line string, column string
- XML-20039: invalid attribute type string in attribute-list declaration at line string, column string
- XML-20040: invalid character string in element content at line string, column string
- XML-20041: entity reference string refers to itself at line string, column string
- XML-20042: invalid Nmtoken: string
- XML-20043: invalid character string in public identifier at line string, column string
- XML-20044: undeclared namespace prefix string used at line string, column string
- XML-20045: attribute string in element string must be an unparsed entity at line string, column string
- XML-20046: undeclared notation string used in unparsed entity string at line string, column string
- XML-20047: missing element declaration string
- XML-20048: duplicate entity declaration string at line string, column string
- XML-20049: invalid use of NDATA in parameter entity declaration at line string, column string
- XML-20050: duplicate attribute declaration string at line string, column string
- XML-20051: duplicate notation declaration string at line string, column string
- XML-20052: undeclared attribute string used at line string, column string
- XML-20053: undeclared element string used at line string, column string
- XML-20054: undeclared entity string used at line string, column string
- XML-20055: invalid document returned by NodeFactory's createDocument
- XML-20056: invalid SAX feature string
- XML-20057: invalid value string passed for SAX feature string
- XML-20058: invalid SAX property string
- XML-20059: invalid value passed for SAX property string
- XML-20060: Error occurred while opening URL string
- XML-20061: invalid byte stream string in UTF8 encoded data
- XML-20062: 5-byte UTF8 encoding not supported
- XML-20063: 6-byte UTF8 encoding not supported
- XML-20064: invalid XML character string
- XML-20065: encoding string doesn't match encoding string in XML declaration
- XML-20066: encoding string not supported
- XML-20067: invalid InputSource returned by EntityResolver's resolveEntity
- XML-20100: Expected string.
- XML-20101: Expected string or string.
- XML-20102: Expected string, string, or string.
- XML-20103: Illegal token in content model.
- XML-20104: Could not find element with ID string.
- XML-20105: ENTITY type Attribute value string does not match any unparsed Entity.
- XML-20106: Could not find Notation string.
- XML-20107: Could not find declaration for element string.
- XML-20108: Start of root element expected.
- XML-20109: PI with the name 'xml' can occur only in the beginning of the document.
- XML-20110: #PCDATA expected in mixed-content declaration.
- XML-20111: Element string repeated in mixed-content declaration.
- XML-20112: Error opening external DTD string.
- XML-20113: Unable to open input source (string).
- XML-20114: Bad conditional section start syntax, expected '['.
- XML-20115: Expected ']]>' to end conditional section.
- XML-20116: Entity string already defined, using the first definition.
- XML-20117: NDATA not allowed in parameter entity declaration.
- XML-20118: NDATA value required.
- XML-20119: Entity Value should start with quote.
- XML-20120: Entity value not well-formed.
- XML-20121: End tag does not match start tag string.
- XML-20122: '=' missing in attribute.
- XML-20123: '>' Missing from end tag.
- XML-20124: An attribute cannot appear more than once in the same start tag.
- XML-20125: Attribute value should start with quote.
- XML-20126: '<' cannot appear in attribute value.
- XML-20127: Reference to an external entity not allowed in attribute value.
- XML-20128: Reference to unparsed entity not allowed in element content.
- XML-20129: Namespace prefix string used but not declared.
- XML-20130: Root element name must match the DOCTYPE name.
- XML-20131: Element string already declared.
- XML-20132: Element cannot have more than one ID attribute.
- XML-20133: Attr type missing.
- XML-20134: ID attribute must be declared #IMPLIED or #REQUIRED.
- XML-20135: Attribute string already defined, using the first definition.
- XML-20136: Notation string already declared.
- XML-20137: Attribute string used but not declared.
- XML-20138: REQUIRED attribute string is not specified.
- XML-20139: ID value string is not unique.
- XML-20140: IDREF value string does not match any ID attribute value.
- XML-20141: Attribute value string should be one of the declared enumerated values.
- XML-20142: Unknown attribute type.
- XML-20143: Unrecognized text at end of attribute value.
- XML-20144: FIXED type Attribute value not equal to the default value string.
- XML-20145: Unexpected text in content of Element string.
- XML-20146: Unexpected text in content of Element string, expected elements string.
- XML-20147: Invalid element string in content of string, expected closing tag.
- XML-20148: Invalid element string in content of string, expected elements string.
- XML-20149: Element string used but not declared.
- XML-20150: Element string not complete, expected elements string.
- XML-20151: Entity string used but not declared.
- XML-20170: Invalid UTF8 encoding.
- XML-20171: Invalid XML character(string).
- XML-20172: 5-byte UTF8 encoding not supported.
- XML-20173: 6-byte UTF8 encoding not supported.
- XML-20180: User Supplied NodeFactory returned a Null Pointer.
- XML-20190: Whitespace required.
- XML-20191: '>' required to end DTD.
- XML-20192: Unexpected text in DTD.
- XML-20193: Unexpected EOF.
- XML-20194: Unable to write to output stream.
- XML-20195: Encoding not supported in PrintWriter.
- XML-20200: Expected string instead of string.
- XML-20201: Expected string instead of string.
- XML-20202: Expected string to be string.
- XML-20205: Expected string.
- XML-20206: Expected string or string.
- XML-20210: Unexpected string.
- XML-20211: string is not allowed in string.
- XML-20220: Invalid InputSource.
- XML-20221: Invalid char in text.
- XML-20230: Illegal change of encoding: from string to string.
- XML-20231: Encoding string is not currently supported.
- XML-20240: Unable to open InputSource.
- XML-20241: Unable to open entity string.
- XML-20242: Error opening external DTD string.
- XML-20250: Missing entity string.
- XML-20251: Cyclic Entity Reference in entity string.
- XML-20280: Bad character (string).
- XML-20281: NMToken must contain atleast one NMChar.
- XML-20282: string not allowed in a PubIdLiteral.
- XML-20284: Illegal white space before optional character in content model.
- XML-20285: Illegal mixed content model.
- XML-20286: Content list not allowed inside mixed content model.
- XML-20287: Content particles not allowed inside mixed content model.
- XML-20288: Invalid default declaration in attribute declaration.
- XML-20500: SAX feature string not recognized.
- XML-20501: SAX feature string not supported.
- XML-20502: SAX property string not recognized.
- XML-20503: SAX property string not supported.
- DOM Error Messages
-
- XML-21000: invalid size string specified
- XML-21001: invalid index string specified; must be between 0 and string
- XML-21002: cannot add an ancestor as a child node
- XML-21003: node of type string cannot be added to node of type string
- XML-21004: document node can have only one string node as child
- XML-21005: node of type string cannot be added to attribute list
- XML-21006: cannot add a node belonging to a different document
- XML-21007: invalid character string in name
- XML-21008: cannot set value for node of type string
- XML-21009: cannot modify descendants of entity or entity reference nodes
- XML-21010: cannot modify DTD's content
- XML-21011: cannot remove attribute; not found in the current element
- XML-21012: cannot remove or replace node; it is not a child of the current node
- XML-21013: parameter string not recognized
- XML-21014: value string of parameter string is not supported
- XML-21015: cannot add attribute belonging to another element
- XML-21016: invalid namespace string for prefix string
- XML-21017: invalid qualified name: string
- XML-21018: conflicting namespace declarations string and string for prefix string
- XML-21019: string object is detached
- XML-21020: bad boundary specified; cannot partially select a node of type string
- XML-21021: node of type string does not support range operation string
- XML-21022: invalid event type: string
- XML-21023: prefix not allowed on nodes of type string
- XML-21024: import not allowed on nodes of type string
- XML-21025: rename not allowed on nodes of type string
- XML-21026: Unrepresentable character in node: string
- XML-21027: Namespace normalization error in node: string
- XML-21997: function not supported on THICK DOM
- XML-21998: system error occurred: string
- XSL Transformation Error Messages
-
- XML-22000: Error while parsing XSL file (string).
- XML-22001: XSL Stylesheet does not belong to XSLT namespace.
- XML-22002: Error while processing include XSL file (string).
- XML-22003: Unable to write to output stream (string).
- XML-22004: Error while parsing input XML document (string).
- XML-22005: Error while reading input XML stream (string).
- XML-22006: Error while reading input XML URL (string).
- XML-22007: Error while reading input XML reader (string).
- XML-22008: Namespace prefix string used but not declared.
- XML-22009: Attribute string not found in string.
- XML-22010: Element string not found in string.
- XML-22011: Cannot construct XML PI with content: string.
- XML-22012: Cannot construct XML comment with content: string.
- XML-22013: Error in expression: string.
- XML-22014: Expecting node-set before relative location path.
- XML-22015: Function string not found.
- XML-22016: Extension function namespace should start with string.
- XML-22017: Literal expected in string function. Found string.
- XML-22018: Parse Error in string function.
- XML-22019: Expected string instead of string.
- XML-22020: Error in extension function arguments.
- XML-22021: Error parsing external document: string.
- XML-22022: Error while testing predicates. Not a nodeset type.
- XML-22023: Literal Mismatch.
- XML-22024: Unknown multiply operator.
- XML-22025: Expression error: Empty string.
- XML-22026: Unknown expression at EOF: string.
- XML-22027: Closing } not found in Attribute Value template.
- XML-22028: Expression value type string not recognized by string.
- XML-22029: Cannot transform child string in string.
- XML-22030: Attribute value string not expected for string.
- XML-22031: Variable not defined: string.
- XML-22032: Found a single } outside expression in Attribute value template.
- XML-22033: Token not recognized:!.
- XML-22034: Namespace definition not found for prefix string.
- XML-22035: Axis string not found
- XML-22036: Cannot convert string to string.
- XML-22037: Unsupported feature: string.
- XML-22038: Expected Node-set in Path Expression.
- XML-22039: Extension function error: Error invoking constructor for string
- XML-22040: Extension function error: Overloaded constructors for string
- XML-22041: Extension function error: Constructor not found for string
- XML-22042: Extension function error: Overloaded method string
- XML-22043: Extension function error: Method not found string
- XML-22044: Extension function error: Error invoking string:string
- XML-22045: Extension function error: Class not found string
- XML-22046: Apply import cannot be called when current template is null.
- XML-22047: Invalid instantiation of string in string context.
- XML-22048: The string element children must precede all other element children of an string element.
- XML-22049: Template string invoked but not defined.
- XML-22050: Duplicate variable string definition.
- XML-22051: only a literal or a reference to a variable or parameter is allowed in id() function when used as a pattern
- XML-22052: no sort key named as: string was defined
- XML-22053: cannot detect encoding in unparsed-text(), please specify
- XML-22054: no such xsl:function with namespace: string and local name: string was defined
- XML-22055: range expression can only accept xs:integer data type, but not string
- XML-22056: exactly one of four group attributes must be present in xsl:for-each-group
- XML-22057: string can only have string as children
- XML-22058: wrong child of xsl:function
- XML-22059: wrong child order of xsl:function
- XML-22060: TERMINATE PROCESSING
- XML-22061: teminate attribute in <xsl:message> can only be yes or no
- XML-22062: string must have at least one string child
- XML-22063: no definition for character-map with qname string
- XML-22064: cannot define character-map with the same name string and the same import precedence
- XML-22065: at least one string must be defined under string
- XML-22066: if select attribute is present, string instructions sequence-constructor must be empty
- XML-22067: if use attribute is present, string instructions sequence-constructor must be empty
- XML-22068: only primary sort key is allowed to have the stable attribute.
- XML-22069: only string or string is allowed.
- XML-22101: DOMSource node as this type not supported.
- XML-22103: DOMResult can not be this kind of node.
- XML-22106: Invalid StreamSource - InputStream, Reader, and SystemId are null.
- XML-22107: Invalid SAXSource - InputSource is null.
- XML-22108: Invalid Source - URL format is incorrect.
- XML-22109: Internal error while reporting SAX events.
- XML-22110: Invalid StreamResult set in TransformerHandler.
- XML-22111: Invalid Result set in TransformerHandler.
- XML-22112: Namespace URI missing }.
- XML-22113: Namespace URI should start with {.
- XML-22117: URL format has problems (null or bad format or missing 'href' or missing '=').
- XML-22121: Could not get associated stylesheet.
- XML-22122: Invalid StreamResult - OutputStream, Writer, and SystemId are null.
- XML-22900: An internal error condition occurred.
- XPath Error Messages
-
- XML-23002: internal xpath error
- XML-23003: XPath 2.0 feature schema-element/schema-attribute not supported
- XML-23006: value does not match required type
- XML-23007: FOAR0001: division by zero
- XML-23008: FOAR0002: numeric operation overflow/unflow
- XML-23009: FOCA0001: Error in casting to decimal
- XML-23010: FOCA0002: invalid lexical value
- XML-23011: FOCA0003: input value too large for integer
- XML-23012: FOCA0004: Error in casting to integer
- XML-23013: FOCA0005: NaN supplied as float/double value
- XML-23014: FOCH0001: invalid codepoint
- XML-23015: FOCH0002: unsupported collation
- XML-23016: FOCH0003: unsupported normalization form
- XML-23017: FOCH0004: collation does not support collation units
- XML-23018: FODC0001: no context document
- XML-23019: FODC0002: Error retrieving resource
- XML-23020: FODC0003: Error parsing contents of resource
- XML-23021: FODC0004: invalid argument to fn:collection()
- XML-23022: FODT0001: overflow in date/time arithmetic
- XML-23023: FODT0002: overflow in duration arithmetic
- XML-23024: FONC0001: undefined context item
- XML-23025: FONS0002: default namespace is defined
- XML-23026: FONS0003: no prefix defined for namespace
- XML-23027: FONS0004: no namespace found for prefix
- XML-23028: FONS0005: base URI not defined in the static context
- XML-23029: FORG0001: invalid value for cast/constructor
- XML-23030: FORG0002: invalid argument to fn:resolve-uri()
- XML-23031: FORG0003: zero-or-one called with sequence containing more than one item
- XML-23032: FORG0004: fn:one-or-more called with sequence containing no items
- XML-23033: FORG0005: exactly-one called with sequence containing zero or more than one item
- XML-23034: FORG0006: invalid argument type
- XML-23035: FORG0007: invalid argument to aggregate function
- XML-23036: FORG0008: both arguments to fn:dateTime have a specified timezone
- XML-23037: FORG0009: base uri argument to fn:resolve-uri is not an absolute URI
- XML-23038: FORX0001: invalid regular expression flags
- XML-23039: FORX0002: invalid regular expression
- XML-23040: FORX0003: regular expression matches zero-length string
- XML-23041: FORX0004: invalid replacement string
- XML-23042: FOTY0001: type error
- XML-23043: FOTY0011: context item is not a node
- XML-23044: FOTY0012: items not comparable
- XML-23045: FOTY0013: type does not have equality defined
- XML-23046: FOTY0014: type exception
- XML-23047: FORT0001: invalid number of parameters
- XML-23048: FOTY0002: type definition not found
- XML-23049: FOTY0021: invalid node type
- XML-23050: FOER0000: unidentified error
- XML-23051: FODC0005: invalid argument to fn:doc
- XML-23052: FODT0003: invalid timezone value
- XML Schema Validation Error Messages
-
- XML-24000: internal error
- XML-24001: attribute string not expected at line string, column string
- XML-24002: can not find element declaration string.
- XML-24003: context-determined element declaration string absent.
- XML-24004: declaration for element string absent.
- XML-24005: element string not assessed
- XML-24006: element string laxly assessed
- XML-24007: missing attribute declaration stringin element string
- XML-24008: type absent for attribute string
- XML-24009: invalid attribute value string
- XML-24010: attribute value string and fixed value string not match
- XML-24011: type of element string is abstract.
- XML-24012: no children allowed for element string with empty content type
- XML-24013: element child string not allowed for simple content
- XML-24014: characters string not allowed for element-only content
- XML-24015: multiple ID attributes in element string at line string, column string
- XML-24016: invalid string value string at line string, column string
- XML-24017: invalid boolean value string at line string, column string
- XML-24018: invalid decimal value string at line string, column string
- XML-24019: invalid float value string at line string, column string
- XML-24020: invalid double value string at line string, column string
- XML-24021: invalid duration string at line string, column string
- XML-24022: invalid date value string at line string, column string
- XML-24023: invalid dateTime value string at line string, column string
- XML-24024: invalid time value string at line string, column string
- XML-24025: invalid gYearMonth value string at line string, column string
- XML-24026: invalid gYear value string at line string, column string
- XML-24027: invalid gMonthDay value string at line string, column string
- XML-24028: invalid gDay value string at line string, column string
- XML-24029: invalid gMonth value string at line string, column string
- XML-24030: invalid hexBinary value string at line string, column string
- XML-24031: invalid base64Binary value string at line string, column string
- XML-24032: invalid anyURI value string at line string, column string
- XML-24033: invalid QName value string at line string, column string
- XML-24034: invalid NOTATION value string at line string, column string
- XML-24035: invalid normalizedString value string at line string, column string
- XML-24036: invalid token value string at line string, column string
- XML-24037: invalid language value string at line string, column string
- XML-24038: invalid NMTOKEN value string at line string, column string
- XML-24039: invalid NMTOKENS value string at line string, column string
- XML-24040: invalid Name value string at line string, column string
- XML-24041: invalid NCName value string at line string, column string
- XML-24042: invalid ID value string at line string, column string
- XML-24043: invalid IDREF value string at line string, column string
- XML-24044: invalid ENTITY value string at line string, column string
- XML-24045: invalid ENTITIES value string at line string, column string
- XML-24046: invalid integer value string at line string, column string
- XML-24047: invalid nonPositiveInteger value string at line string, column string
- XML-24048: invalid negativeInteger value string
- XML-24049: invalid long value string at line string, column string
- XML-24050: invalid int value string at line string, column string
- XML-24051: invalid short value string at line string, column string
- XML-24052: invalid byte value string at line string, column string
- XML-24053: invalid nonNegativeInteger value string at line string, column string
- XML-24054: invalid unsignedLong value string at line string, column string
- XML-24055: invalid unsignedInt value string at line string, column string
- XML-24056: invalid unsignedShort value string at line string, column string
- XML-24057: invalid unsignedByte value string at line string, column string
- XML-24058: value string must be valid with respect to one member type
- XML-24059: element string not expected at line string, column string
- XML-24060: element string abstract
- XML-24061: element string not nillable
- XML-24062: no character or element children allowed for nil content string
- XML-24063: nil element does not satisfy fixed value constraint
- XML-24064: xsi:type not a QName at line string, column string
- XML-24065: xsi:type string not resolved to a type definition
- XML-24066: local type string not validly derived from the type of element string
- XML-24067: value string not in enumeration
- XML-24068: invalid facet string for type string
- XML-24069: too many fraction digits in value string at line string, column string
- XML-24070: missing ID definition for ID reference string at line string, column string
- XML-24071: duplicate ID string at line string, column string
- XML-24072: duplicate key sequence string
- XML-24073: target node set not equals to qualified node set for key string
- XML-24074: element member string in key sequence is nillable
- XML-24075: missing key sequence for key reference string
- XML-24076: incorrect length of value string
- XML-24077: value string greater than or equal to maxExclusive
- XML-24078: value string greater than the maxInclusive
- XML-24079: value length of string greater than maxLength
- XML-24080: value string smaller or equals to minExclusive
- XML-24081: value string smaller than minInclusive
- XML-24082: value string shorter than minLength
- XML-24083: wildcard particle in the content of element string not done
- XML-24084: element particle string not done
- XML-24085: model group string in the content of element string not done
- XML-24086: invlid literal string with respect to pattern facet string
- XML-24087: undefined type string
- XML-24088: undeclared attribute string
- XML-24089: undeclared element string
- XML-24090: undefined attribute group string
- XML-24091: undefined model group string
- XML-24092: undeclared notation string
- XML-24093: too many digits in value string at line string, column string
- Schema Representation Constraint Error Messages
-
- XML-24100: element string must belong to XML Schema namespace
- XML-24101: can not build schema from location string
- XML-24102: can not resolve schema by target namespace string
- XML-24103: invalid annotation representation at line string, column string
- XML-24104: multiple annotations at line string, column string
- XML-24105: annotation must be the first element at line string, column string
- XML-24106: attribute wildcard before attribute declaration at line string, column string
- XML-24107: multiple attribute wildcard
- XML-24108: default string and fixed string both present
- XML-24109: default value string conflicts with attribute use stringXML-24109: default value string conflicts with attribute use string
- XML-24110: missing name or ref attribute
- XML-24111: both name and ref presented in attribute declaration
- XML-24112: ref conflicits with form, type, or simpleType child
- XML-24113: type attribute conflicts with simpleType child
- XML-24114: intersecton of attribute wildcard is not expressible
- XML-24115: circular attribute group reference string
- XML-24116: circular group reference string
- XML-24117: base type string for complexContent is not complex type
- XML-24118: simple content required in base type string
- XML-24119: properties specified with element reference string
- XML-24120: simpleType and complexType can not both present in element declaration string
- XML-24121: imported namespace string must different from namespace string
- XML-24122: target namespace string required
- XML-24123: namespace stringis different from expedted targetNamespace string
- XML-24124: targetNamespace string not expected in schema
- XML-24125: can not include schema fromstring
- XML-24126: included targetNamespace string must the same as string
- XML-24127: no-namespace schema can not include schema with target namespace string
- XML-24128: itemType attribute conflicits with simpleType child
- XML-24129: prefix of qname string can not be resolved
- XML-24130: redefined schema has different namespace. line string column string
- XML-24131: no-namespace schema can only redefine schema without targetNamespace
- XML-24132: type derivation string must be restriction
- XML-24132: type string must redefine itself at line string, column string
- XML-24133: group string can have only one self reference in redefinition
- XML-24134: self reference of group string must not have minOccurs or maxOccurs other than 1 in redefinition
- XML-24135: redefined group stringis not a restriction of its orginal group
- XML-24236: attribute group string can have only one self reference in redefinition
- XML-24136: redefined attribute group string must be a restriction of its orginal group
- XML-24137: restriction must not have both base and simpleType child
- XML-24138: simple type restriction must have either base attribute or simpleType child
- XML-24139: neitehr itemType or simpleType child present for list
- XML-24140: itemType and simpleType child can not both be present in list type.
- XML-24141: circular union type is disallowed
- XML-24142: facet string can not be specified more than once
- XML-24143: memberTypes and simpleType child can not both be absent in union
- XML-24144: facets can only used for restriction
- Schema Component Constraint Error Messages
-
- XML-24201: duplicate attribute string declaration
- XML-24202: more than one attributes with ID type not allowed
- XML-24203: invalid value constraint string
- XML-24204: value constraint string not allowed for ID type
- XML-24205: fixed value string does not match string in attribute declaration
- XML-24206: value constraint must be fixed to match that in attribute declaration
- XML-24207: invalid xpath expression string
- XML-24208: invalid field xpath string
- XML-24209: maxOccurs in element string of All group must be 0 or 1
- XML-24210: All group has to form a content type.
- XML-24211: All group has to form a content type.
- XML-24212: type string does not allow facet string
- XML-24213: wildcard intersection is not exprssible
- XML-24214: base type not allow string derivation
- XML-24215: complex type string is not a derivation of type string
- XML-24216: must specify a particle in extened content type
- XML-24217: content type string conflicts with base type's content type string
- XML-24218: inconsistent local element declarations string
- XML-24219: element string is not valid substitutable for element string
- XML-24220: itemType string can not be list
- XML-24221: cricular union string not allowed
- XML-24222: ambiguous particles string
- XML-24223: invalid particle extension
- XML-24224: invalid particle restriction
- XML-24225: simple type string does not allowed restriction
- XML-24226: invalid derivation from base type string
- XML-24227: atomic type can not restrict list string
- XML-24228: base type can not be ur-type in restriction
- XML-24229: base type of list must be list or ur-type
- XML-24230: base type of union must be union or ur-type
- XML-24231: element default stringrequires mixed content to be emptiable
- XML-24232: element default string requires mixed content or simple content
- XML-24233: element default string must be valid to its content type
- XML-24234: wrong field cardinality for keyref string
- XML-24235: complex type can only extend simple type string
- XML-24236: cricular type definition string
- XML-24237: base type string must be complex type
- XML-24238: attribute string not allowed in base type
- XML-24239: required attribute string not in restriction
- XML-24240: no correspoonding attribue wildcard in bas type string
- XML-24241: base type string must have simple content or emptiable
- XML-24242: base type string must have empty content or emptiable
- XML-24243: enumeration facet required for NOTATION
- XML-24244: invalid value string in enumeration
- XML-24245: default value stringis element type invalid
- XML-24246: invalid substitutionGroup string, type invalid
- XML-24247: ID type does not allow value constraint string
- XML-24248: fractionDigits stringgreater than totalDigits string
- XML-24249: length facet can not be specified with minLength or maxLength
- XML-24250: length string not the same as length in base type's
- XML-24251: maxExclusive greater than its original
- XML-24252: minInclusive greater than or equal to maxExclusive
- XML-24253: maxLength is greater than that in base type
- XML-24254: circular group stringdisallowed
- XML-24256: minExclusive must be less than or equal to maxExclusive
- XML-24257: minExclusive stringmust be less than maxInclusive
- XML-24258: invalid minExclusive string
- XML-24259: invalid minExclusive string
- XML-24260: invalid minExclusive string
- XML-24261: invalid minExclusive string
- XML-24262: minInclusive string must not be greater than maxInclusive
- XML-24263: Can not specify both minInclusive and minExclusive
- XML-24264: invalid minInclusive string
- XML-24265: invalid minInclusive string
- XML-24267: invalid minInclusive string
- XML-24268: invalid minInclusive string
- XML-24269: invalid minLength string
- XML-24270: invalid minLength string
- XML-24271: can not declare xmlns attribute
- XML-24272: no xsi for targetNamespace
- XML-24272: minOccurs is greater than maxOccurs
- XML-24281: maxOccurs must greater than or equal to 1
- XML-24282: incorrect Notation properties
- XML-24283: particle's range is not valid restriction
- XML-24284: sequence group is not valid derivation of choice group
- XML-24285: element string is not valid restriction of element string
- XML-24286: element string is not valid restriction of wildcard
- XML-24287: group is not valid restriction of wildcard
- XML-24288: group any is not valid restriction
- XML-24289: invalid restriction of all or sequence group
- XML-24290: wildcard is not valid restriction
- XML-24291: sequence is not a valid restriction of all
- XML-24292: duplicate component definitions string
- XML-24293: Incorrect simple type definition properties
- XML-24294: wildcard is not a subset of its super
- XML-24295: totalDigits stringis greater than string in base type
- XML-24296: whiteSpace string can not restrict base type's string
- XML-24297: circular substitution group string
- XSQL Server Pages Error Messages
-
- XML-25001: Cannot locate requested XSQL file. Check the name.
- XML-25002: Cannot acquire database connection from pool: string
- XML-25003: Failed to find config file string in CLASSPATH.
- XML-25004: Could not acquire a database connection named: string
- XML-25005: XSQL page is not well-formed.
- XML-25006: XSLT stylesheet is not well-formed: string
- XML-25007: Cannot acquire a database connection to process page.
- XML-25008: Cannot find XSLT Stylesheet: string
- XML-25009: Missing arguments on command line
- XML-25010: Error creating: string\nUsing standard output.
- XML-25011: Error processing XSLT stylesheet: string
- XML-25012: Cannot Read XSQL Page
- XML-25013: XSQL Page URI is null; check exact case of file name.
- XML-25014: Resulting page is an empty document or had multiple document elements.
- XML-25015: Error inserting XML Document
- XML-25016: Error parsing posted XML Document
- XML-25017: Unexpected Error Occurred
- XML-25018: Unexpected Error Occurred processing stylesheet string
- XML-25019: Unexpected Error Occurred reading stylesheet string
- XML-25020: Config file string is not well-formed.
- XML-25021: Serializer string is not defined in XSQL configuration file
- XML-25022: Cannot load serializer class string
- XML-25023: Class string is not an XSQL Serializer
- XML-25024: Attempted to get response Writer after getting OutputStream
- XML-25025: Attempted to get response OutputStream after getting Writer
- XML-25026: Stylesheet URL references an untrusted server.
- XML-25027: Failed to load string class for built-in xsql:string action.
- XML-25028: Error reading string. Check case of the name.
- XML-25029: Cannot load error handler class string
- XML-25030: Class string is not an XSQL ErrorHandler
- XML-25100: You must supply a string attribute.
- XML-25101: Fatal error in Stylesheet Pool
- XML-25102: Error instantiating class string
- XML-25103: Unable to load class string
- XML-25104: Class string is not an XSQLActionHandler
- XML-25105: XML returned from PLSQL agent was not well-formed
- XML-25106: Invalid URL string
- XML-25107: Error loading URL string
- XML-25108: XML Document string is not well-formed
- XML-25109: XML Document returned from database is not well-formed
- XML-25110: XML Document in parameter string is not well-formed
- XML-25111: Problem including string
- XML-25112: Error reading parameter value
- XML-25113: Error loading XSL transform string
- XML-25114: Parameter string has a null value
- XML-25115: No posted document to process
- XML-25116: No query statement supplied
- XML-25117: No PL/SQL function name supplied
- XML-25118: Stylesheet URL references an untrusted server.
- XML-25119: You must supply either the string or string attribute.
- XML-25120: You selected fewer than the expected string values.
- XML-25121: Cannot use 'xpath' to set multiple parameters.
- XML-25122: Query must be supplied to set multiple parameters
- XML-25123: Error reading string. Check case of the name.
- XML-25124: Error printing additional error information.
- XML-25125: Only one of (string) attributes is allowed.
- XML-25126: One of (string) attributes must be supplied.
- XML Pipeline Error Messages
-
- XML-30000: Error ignored in string: string
- XML-30001: Error occured in execution of Process
- XML-30002: Only XML type(s) string allowed.
- XML-30003: Error creating/writing to output string
- XML-30004: Error creating base url string
- XML-30005: Error reading input string
- XML-30006: Error in processing pipedoc Error element
- XML-30007: Error converting output to xml type required by dependent process
- XML-30008: A valid parameter target is required
- XML-30009: Error piping output to input
- XML-30010: Process definition element string needs to be defined
- XML-30011: ContentHandler not available
- XML-30012: Pipeline components are not compatible
- XML-30013: Process with output label string not found
- XML-30014: Pipeline is not complete, missing output/outparam label called string
- XML-30016: Unable to instantiate class
- XML-30017: Target is up-to-date, pipeline not executed
- Java API for XML Binding (JAXB) Error Messages
-
- XML-32202: a problem was encountered because multiple <schemaBindings> were defined.
- XML-32203: a problem was encountered because multiple <class> name annotations were defined on node string.
- XML-32204: a problem was encountered because the name in <class> declaration contained a package name prefix string which was not allowed.
- XML-32205: a problem was encountered because the property customization was not specified correctly on node string.
- XML-32206: a problem was encountered because the javaType customization was not specified correctly on node string.
- XML-32207: a problem was encountered in declaring the baseType customization on the node string.
- XML-32208: a problem was encountered because multiple baseType customizations were declared on the node string.
- XML-32209: a problem was encountered because multiple javaType customizations were declared on the node string.
- XML-32210: a problem was encountered because invalid value was specified on customization of string.
- XML-32211: a problem was encountered because incorrect <schemaBindings> customization was specified.
- XML-32212: the <class> customization did not support specifiying the implementation class using implClass declaration. The implClass declaration specified on node string was ignored.
- XML-32213: the <globalBindings> customization did not support specifiying user specific class that implements java.util.List. The collectionType declaration was ignored.
- TXU Error Messages
-
- General TXU Error Messages
-
- TXU-0001: Fatal Error
- TXU-0002: Error
- TXU-0003: Warning
- DLF Error Messages
-
- TXU-0100: parameter string in query string not found
- TXU-0101: incompatible attributes col and constant coexist at string in query string
- TXU-0102: node string not found
- TXU-0103: element string lacks content
- TXU-0104: element string with SQL string lacks col or constant attribute
- TXU-0105: SQL exception string while processing SQL string
- TXU-0106: no data for column string selected by SQL string
- TXU-0107: datatype string not supported
- TXU-0108: missing maxsize attribute for column string
- TXU-0109: a text length of string for string exceeds the allowed maximum of string
- TXU-0110: undeclared column string in row string
- TXU-0111: lacking column data for string in row string
- TXU-0112: undeclared query parameter string for column string
- TXU-0113: incompatible attribute string with a query on column string
- TXU-0114: DLF parse error (string) on line string, character string in string
- TXU-0115: The specified date string string has an invalid format
- TransX Informational Messages
-
- TXU-0200: duplicate row at string
- TransX Error Messages
-
- TXU-0300: document string not found
- TXU-0301: file string could not be read
- TXU-0302: archive string not found
- TXU-0303: schema string not found in string
- TXU-0304: archive path for string not found
- TXU-0305: no database connection on string call for string
- TXU-0306: null tablename given; access denied
- TXU-0307: lookup-keys could not be determined string
- TXU-0308: binary file string not found
- TXU-0309: a file size of string exceeds the allowed maximum of 2,000 bytes
- Assertion Messages
-
- TXU-0400: missing SQL statement element on string
- TXU-0401: missing node string
- TXU-0402: invalid flag string
- TXU-0403: internal error string
- TXU-0404: unexpected Exception string
- Usage Description Messages
-
- TXU-0500: XML data transfer utility
- TXU-0501: Parameters are as follows:
- TXU-0502: JDBC connect string
- TXU-0503: You can omit the connect string information through the '@' symbol.
- TXU-0504: Then jdbc:oracle:thin:@ will be supplied.
- TXU-0505: database username
- TXU-0506: database password
- TXU-0507: data file name or URL
- TXU-0508: Options:
- TXU-0509: update existing rows
- TXU-0510: raise exception if a row is already existing
- TXU-0511: print data in the predefined format
- TXU-0512: save data in the predefined format
- TXU-0513: print the XML to load
- TXU-0514: print the tree for update
- TXU-0515: omit validation
- TXU-0516: validate the data format and exit without loading
- TXU-0517: preserve whitespace
- TXU-0518: Examples:
- XSU Error Messages
-
- Keywords and Syntax for Error Messages
-
- XSUK-0001: DOCUMENT
- XSUK-0002: ROWSET
- XSUK-0003: ROW
- XSUK-0004: ERROR
- XSUK-0005: num
- XSUK-0006: item
- Generic Error Messages
-
- XSUE-0000: Internal Error -- Exception Caught string
- XSUE-0001: Internal Error -- string
- XSUE-0002: string is not a scalar column. The row id attribute can only get values from scalar columns.
- XSUE-0003: string is not a valid column name.
- XSUE-0004: This object has been closed. If you would like the object not to be closed implicitly between calls, see the string method.
- XSUE-0005: The row-set enclosing tag and the row enclosing tag are both omitted; consequently, the result can consist of at most one row which contains exactly one column which is not marked to be an XML attribute.
- XSUE-0006: The row enclosing tag or the row-set enclosing tag is ommitted; consequently to get a well formed XML document, the result can only consist of a single row with multiple columns or multiple rows with exactly one column which is not marked to be an XML attribute.
- XSUE-0007: Parsing of the sqlname failed -- invalid arguments.
- XSUE-0008: Character string is not allowed in an XML tag name.
- XSUE-0009: this method is not supported by string class. Please use string instead.
- XSUE-0010: The number of bind names does not equal the number of bind values.
- XSUE-0011: The number of bind values does not match the number of binds in the SQL statement.
- XSUE-0012: Bind name identifier string does not exist in the sql query.
- XSUE-0013: The bind identifier has to be of non-zero length.
- XSUE-0014: Root node supplied is null.
- XSUE-0015: Invalid LOB locator specified.
- XSUE-0016: File string does not exit.
- XSUE-0017: Can not create oracle.sql.STRUCT object of a type other than oracle.sql.STRUCT (i.e. ADT).
- XSUE-0018: Null is not a valid DocumentHandler.
- XSUE-0019: Null and empty string are not valid namespace aliases.
- XSUE-0020: to use this method you will have to override it in your subclass.
- XSUE-0021: You are using an old version of the gss library; thus, sql-xml name escaping is not supported.
- XSUE-0022: cannot create XMLType object from opaque base type: string
- Query Error Messages
-
- XSUE-0100: Invalid context handle specified.
- XSUE-0101: In the FIRST row of the resultset there is a nested cursor whose parent cursor is empty; when this condition occurs we are unable to generate a dtd.
- XSUE-0102: string is not a valid IANA encoding.
- XSUE-0103: The resultset is a "TYPE_FORWARD_ONLY" (non-scrollable); consequently, xsu can not reposition the read point. Furthermore, since the result set has been passed to the xsu by the caller, the xsu can not recreate the resultset.
- XSUE-0104: input character is invalid for well-formed XML: string
- DML Error Messages
-
- XSUE-0200: The XML element tag string does not match the name of any of the columns/attributes of the target database object.
- XSUE-0201: NULL is an invalid column name.
- XSUE-0202: Column string, specified to be a key column, does not not exits in table string.
- XSUE-0203: Column string, specified as column to be updated, does not exist in the table string.
- XSUE-0204: Invalid REF element - string - attribute string missing.
- XSUE-0206: Must specify key values before calling update routine. Use the string function.
- XSUE-0207: UpdateXML: No columns to update. The XML document must contain some non-key columns to update.
- XSUE-0208: The key column array must be non empty.
- XSUE-0209: The key column array must be non empty.
- XSUE-0210: No rows to modify -- the row enclosing tag missing. Specify the correct row enclosing tag.
- XSUE-0211: string encountered during processing ROW element string in the XML document.
- XSUE-0212: string XML rows were successfully processed.
- XSUE-0213: All prior XML row changes were rolled back.
- Pieces of Error Messages
-
- XSUE-0300: Note
- XSUE-0301: Exception string caught: string
- XSUE-0302: column
- XSUE-0303: name
- XSUE-0303: invalid
- XSUE-0304: xml document
- XSUE-0305: template