|How do I import Xerces-J into Visual Age for Java|
Why does VisualAge for Java 2.0 report problems when I import
the Xerces-J parser?
The current version of the Xerces-J 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:
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 Xerces-J
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.