This release uses Swing 1.1 (JFC 1.1). Swing is only used by the sample programs and is not required by the parser itself.

To build &ParserName; you need the Java Development Kit (JDK) version 1.2 (or higher) installed on your machine. The actual build is performed by the Ant program which is written in Java and is a subproject of the Apache Ant project. The build also requires a few other tools but all of the tools you need (including Ant) are contained in the &ParserName;-tools.&parserversion;.zip file, packaged separately. Go to the &ParserName; download page to download the tools package and then extract it in the same location as the source package.

Once you have extracted both the source and tools packages in the same directory, you can invoke a build by either using the "build.bat" file for Windows platforms or the "build.sh" file for UNIX platforms. Before invoking either one of these scripts, though, be sure to set the JAVA_HOME environment variable to the installed location of your JDK.

The script will invoke the Ant build program for you which displays the list of allowed build targets. To only compile the source files, type "build compile" (on Windows platforms) at the command line in the directory where you extracted &ParserName;; to build the Jar files, type "build jars"; and to build everything, including documentation, type "build all".

To regenerate the API documentation, you need to set up your environment to build &ParserName;. Instead of typing "build all", you type "build javadocs".

• Why does VisualAge for Java 2.0 report problems when I import the &ParserName; parser?
  The current version of the &ParserName; parser uses Swing 1.1, while VisualAge for Java 2.0 comes with Swing 1.0.2. The free update for the Professional version of VisualAge for Java 2.0 installs Swing 1.0.3. The most important difference between Swing 1.0.2 - 1.0.3 and 1.1 is the Java package was changed from com.sun.java.swing.* to javax.swing.*.
  To fix the errors, you must download the Java Foundation Classes 1.1 with Swing 1.1 from Sun's Java home page and import the "swingall.jar" file into VisualAge for Java 2.0. The Swing 1.1 package can be found at the following URL:
  http://java.sun.com/products/jfc/index.html
  Refer to the VisualAge for Java 2.0 documentation for information about how to import a JAR file into the repository and add that code to your workspace.
• Are there any other tips for importing the &ParserName; parser into VisualAge for Java 2.0?
  The most useful tip applies to any updated code that you import into the VisualAge for Java 2.0 product. Before updating code, do the following:
  1. version the old code
  2. delete it from your workspace
  3. import the new code
  Deleting code from your workspace does not actually delete the code permanently - the versioned code is moved to the repository where it can be retrieved later. Be aware, though, that removing code from your workspace will cause problems with all of the other classes that use that code. VisualAge for Java 2.0 will flag them as errors but this situation is temporary. When you import the new code, the errors found when deleting the old code will be fixed.
  If you are unsure as to how to perform any of these steps, refer to the VisualAge for Java 2.0 documentation.

Prerequisites (available from http://developer.apple.com/java/):

• MRJ 2.1 (this is the most recent version of the JVM)
• MRJ SDK 2.1 (this is the most recent version of the Java developer tools)

Instructions (other variations would work also):

1. Download the .tar.gz file containing &ParserName;.
2. Use Stuffit Expander(tm), Suntar, or some other Macintosh tool that supports the .tar.gz format to expand the downloaded file.
3. JBindery, part of MRJ SDK 2.1, is used to create a double-clickable Java application with the necessary configuration information built in. It is analogous to writing a .bat or .sh script.
4. To run the dom.DOMWriter example:
1. Double click on JBindery to start it up.
2. Click on the Classpath panel.
3. Click on the "Add .zip File" button and add both the "xerces.jar" and "xercesSamples.jar" files.
4. Click on the Command panel.
5. Enter "dom.Writer" as the Class name. Enter "data/personal.xml" in the Optional parameters box.
6. Click on Save Settings button, pick a name such as "Run dom.Writer" for the file, and be sure that "Save as Application" is selected (this is the default) and save the file.
7. Quit JBindery.
8. You can now double click on the file you created in step (f) to run the XJParse example.

The Visual Cafe debugger is set to trap ArrayIndexOutOfBoundsException exceptions by default. &ParserName; sometimes uses ArrayIndexOutOfBoundsException internally to signal exceptional, but not erroneous conditions. In order to run &ParserName; inside Visual Cafe's debugger, you need to turn off the trapping of these exceptions.

To do this:

1. Select the "Options" item in the "Project" menu.
2. Select the "Debugger" tab in the dialog which appears.
3. Select "Exceptions" from the popup menu.
4. Remove the check from the checkbox for java.lang.ArrayIndexOutOfBoundsException.