|Oracle9i XML Developer's Kits Guide - XDK
Release 2 (9.2)
Part Number A96621-01
This appendix describes the XDK for Java specifications and quick references for each XML component for Java. The quick references list the main APIs, classes, and associated methods for each XDK for Java component.
This appendix contains the following sections:
The XML Parser for Java methods are listed in these places:
The Oracle XML Parser for Java, Version 2 specifications follow:
Operating Systems: Any with Java 1.1.x support
JAVA: JDK 1.1.x. or later.
The contents of both the Windows and UNIX versions are identical. They are simply archived differently for operating system compatibility and your convenience.
Documentation for Oracle XML Parser for Java is located in the doc/ directory in your install area.
The readme.html file in the root directory of the archive contains release specific information including bug fixes, API additions, and so on.
Oracle XML Parser is an early adopter release and is written in Java. It will check if an XML document is well-formed and, optionally, if it is valid. The parser will construct a Java object tree which can be accessed. It also contains an integrated XSLT processor for transforming XML documents.
The parser conforms to the following W3C Recommendations:
The parser also conforms to the following W3C Proposed Recommendations:
In addition, the parser implements the following interfaces defined by the XML development community:
The XML Parser for Java (and the XSQL Servlet) currently support:
UTF-8 is the default encoding if none is specified. Any other ASCII or EBCDIC based encodings that are supported by the JDK may be used.However, they must be specified in the format required by the JDK instead of as official character set names defined by IANA.
The parser also provides error recovery. It will recover from most errors and continue processing until a fatal error is encountered.
Oracle XML Class Generator for Java requires Oracle XML Parser for Java. The XML Document, printed by the generated classes, confirms to the W3C recommendation for Extensible Markup Language (XML) 1.0. Oracle XML Class Generator can optionally generate validating Java source files. It also optionally generates Javadoc comments in the source files.
Oracle XML Class Generator supports the following encodings for printing the XMLDocument:
UTF-8, UTF-16, ISO-10646-UCS-2, ISO-10646-UCS-4, US-ASCII, EBCDIC-CP-US, ISO-8859-1, and Shift_SJIS.
ASCII is the default encoding if none is specified. Any other ASCII or EBCDIC based encodings that are supported by the JDK can be used.
You can download XSQL Servlet distribution from:
To extract the contents of XSQL Servlet distribution, do the following:
using the pkzip25 command-line tool or the WinZip visual archive extraction tool.
XSQL Servlet comes bundled with the Oracle Web-to-go server that is pre-configured to use XSQL Pages. The Web-to-go web server is a single-user server, supporting the Servlet 2.1 API, used for mobile application deployment and for development. This is a great way to try XSQL Pages out on your Windows machine before delving into the details of configuring another Servlet Engine to run XSQL Pages.
The Web-to-go Web server is part of Oracle's development and deployment platform for mobile applications. For more information on Web-to-go, see http://www.oracle.com/mobile.
Windows NT users can get started quickly with XSQL Pages by following these steps:
If you get an error starting this script, edit the xsql-wtg.bat file to properly set the two environment variables JAVA and XSQL_HOME to appropriate values for your machine.
REM ---------------------------------------------- REM Set the 'JAVA' variable equal to the full path REM of your Java executable. REM ---------------------------------------------- set JAVA=J:\java1.2\jre\bin\java.exe set XSQL_HOME=C:\xsql REM ---------------------------------------------- REM Set the 'XSQL_HOME' variable equal to the full REM path of where you install the XSQL Servlet REM distribution. REM ----------------------------------------------
Then, repeat the two preceding steps.
If you get an error connecting to the database when you try the demos, you'll need to go on to the next section, then try the preceding steps again after setting up your database connection information correctly in the XSQLConfig.xml file.
The demos are set up to use the SCOTT schema on a database on your local machine (that is, the machine where the web server is running). If you are running a local database and have a SCOTT account whose password is TIGER, then you are all set. Otherwise, you need to edit the
.\xsql\lib\XSQLConfig.xml file to correspond to your appropriate values for username, password, dburl, and driver values for the connection named "demo".
<?xml version="1.0" ?> <XSQLConfig> : <connectiondefs> <connection name="demo"> <username>scott</username> <password>tiger</password> <dburl>jdbc:oracle:thin:@localhost:1521:ORCL</dburl> <driver>oracle.jdbc.driver.OracleDriver</driver> </connection> <connection name="lite"> <username>system</username> <password>manager</password> <dburl>jdbc:Polite:POlite</dburl> <driver>oracle.lite.poljdbc.POLJDBCDriver</driver> </connection> </connectiondefs> : </XSQLConfig>
UNIX users and any user wanting to install the XSQL Servlet on other web servers should continue with the instructions below depending on the web server you're trying to use. In every case, there are 3 basic steps:
For convenience, the xsqlservlet_v184.108.40.206.tar.gz and xsqlservlet_v220.127.116.11.zip distributions include the .jar files for the Oracle XML Parser for Java (V2), the Oracle XML SQL Utilities for Java, and the 8.1.6 JDBC driver in the .\lib subdirectory, along with Oracle XSQL Pages' own .jar archive.
The following lists the XSQL servlet specifications: