jar xvf xml-tr1.zip
Alternatively, use an UnZip utility you may already
have. Info-ZIP
is one such utility, and is available on a variety of
operating systems.
LICENSE | The license applying to this software |
apidoc/* | Javadoc generated files presenting library APIs |
examples/* | Example files, in subdirectories |
examples/index.html | Index to the example files |
readme.html | README for this release |
install.html | This file |
relnotes.html | Release notes |
src.zip | ZIP Archive file containing source code. |
xml.jar | Java Archive file containing classes |
On Solaris, if you've installed the JDK in /java:
% set path=(/java/bin $path) % setenv JAVA_HOME /javaOn Win32 systems, if you have installed the JDK in D:\java:
C:\> set PATH=D:\java\bin;%PATH% C:\> set JAVA_HOME=D:\java
$XML/xml.jar
(Solaris)
$XML\xml.jar
(Win32)
If you are using JDK 1.2 you may wish to install this JAR file as an extension, copying it to the jre/lib/ext directory. This eliminates the need to modify class paths. (This technique may also be used with the Java Plug-in.)
To install this JAR file as an extension to the Java Web Server, version 1.1.6 and later, copy it into the lib directory of the Java Web Server distribution and restart the server process. (This can't be done through the administration user interface; you need to use operating system level commands.)
Similarly, to use this package in Netscape Communicator 4.5, you may wish to install this JAR file as an extension, copying it into the Program/Java/Classes directory. This eliminates the need to download this JAR file with other applet code in many cases.
On Solaris, the Makefile for each sample should work with at most minimal changes (as may be noted in the Makefile). It will build the classes as necessary, if the JDK is set up correctly. For example:
% cd $XML/examples/simple % make ... output %
Developers using Win32 will need to read the Makefiles and perform the analagous procedures as needed for their particular development environment. At this time, the pathnames use POSIX/UNIX/Linux style pathnames (slashes) rather than backslashes (as used by Win32), and path separators use colons not semicolons.