1-4 Programming XML for Oracle WebLogic Server
For information about parsing XML documents, see Section 3.2, Parsing XML
Documents.
1.6.1.1 Difference In Default Parsers Between Versions 8.1 and 9.1 of WebLogic Server
The default parser in Versions 8.1and previous of WebLogic Server was one that was based on Apaches Xerces parser and whose package name started with
weblogic.apache.xerces.. In Version 9.1 of WebLogic Server, this parser has been deprecated. Instead, the default parser is the same one that is shipped in JDK 5.0.
For backward compatibility, the weblogic.apache.xerces. parser is still available in Version 9.1 of WebLogic Server, although it is deprecated and Oracle
highly recommends you do not use it since it will not be available in future versions. If, however, you need to temporarily continue using this parser, you must use the
Administration Console to configure a parser other than the default for your WebLogic Server instance by updating, or creating, a new XML Registry and setting
the default implementation classes for SAX and DOM parser factory interfaces, as indicated in
Table 1–1 .
For information about creating an XML Registry, see Chapter 9, Administering
WebLogic Server XML.
1.6.2 XML Document Transformer
WebLogic Server uses, by default, the XML transformer that is included in the JDK Version 5.0.
You can also use any other XML transformer of your choice by using the Administration Console to configure it in the XML Registry. You can configure a
single instance of WebLogic Server to use one transformer for a particular application and use another transformer for a different application.
For more information about transforming XML documents, see Section 3.4,
Transforming XML Documents.
1.6.3 Streaming API for XML StAX Implementation
WebLogic Server includes an implementation of the Streaming API for XML StAX. For more information, see
Chapter 4, Using the Streaming API for XML StAX.
1.6.4 WebLogic XPath API
The WebLogic XPath API contains all of the classes required to perform XPath matching against a document represented as a DOM, an XMLInputStream, or an
XMLOutputStream.
For more information, see Section 5.2, Using the WebLogic XPath API.
Table 1–1 Default Implementation Classes for SAX and DOM Parser Factory Interfaces
Parser Factory Interface Implementation Class
DOM DocumentBuilderFactory
weblogic.apache.xerces.jaxp.DocumentBuilderFactoryImpl SAX SAXParserFactory
weblogic.apache.xerces.jaxp.SAXParserFactoryImpl
Introduction and Roadmap 1-5
1.6.5 JAXP Pluggability Layer Implementation
Java API for XML Processing JAXP 1.2 is a Java-standard, parser-independent API for XML. For more information on JAXP, see
Section 2.7, What Is JAXP?.
1.6.6 Java API for XML Registries Implementation
The Java API for XML Registries JAXR API, described at http:java.sun.comxmljaxrindex.jsp
, provides a uniform and standard Java API for accessing different kinds of registries, in particular XML registries used in
Web Service applications. For more information, see
Section 5.1, Using the Java API for XML Registries JAXR API.
1.6.7 WebLogic Servlet Attributes
