JavaTM XML Pack Summer 02 update Bundle Release Notes 

This release of the JavaTM XML Pack has been tested with various configurations, using Tomcat 4.0.3 and the J2EETM 1.3.1 with the JavaTM 2 SDK, Standard Edition versions 1.3.1_03 and 1.4 on the following platforms: This release includes: For release notes for each of these technologies see:

To check if any of the information in this file has been updated, see the online version.

Redistributable Components

Redistribution of the entire Java XML Pack is subject to this license.

The following Java XML Pack components are individually redistributable. Redistribution of a component entails the redistribution of all files comprising the component and any dependent components.

Component Files
JAXP jaxp-api.jar, dom.jar, sax.jar, xalan.jar, xercesImpl.jar, xsltc.jar
SAAJ saaj-api.jar, saaj-ri.jar, activation.jar, commons-logging.jar, dom4j.jar, mail.jar, JAXP
JAXM jaxm-api.jar, jaxm-provider, jaxm-provideradmin, jaxm-runtime.jar, SAAJ, JAXP
JAXR jaxr-api.jar, jaxr-ri.jar, soap.jar, castor-0.9.3.9-xml.jar, fscontext.jar, jaas.jar, jcert.jar, jnet.jar, jsse.jar, providerutil.jar, SAAJ, JAXP
JAX-RPC jaxrpc-api.jar, jaxrpc-ri.jar, SAAJ, JAXP

Environment Variables

To use the Java XML Pack technologies, you need to set the home directory for each technology as follows:

where <JAVA_XML_PACK_INSTALL> is the directory where the Java XML Pack bundle was unpacked.

To build and run the examples, you will also need to set environment variables described in the next section.

Building and Running the Examples

To use the Java XML Pack technologies, you need a version of the Java 2 Platform, Standard Edition (J2SETM). To download J2SE:

  1. Decide where you want J2SE to be installed.
  2. Go to the following web site:

    http://java.sun.com/j2se

  3. Download and install either J2SE v1.4 or v1.3.1 SDK. The Java XML Pack has been tested with both versions.
  4. Set the environment variable JAVA_HOME to the location of your J2SE installation.

To build some of the examples, you need the ant 1.4.1 build tool. To install ant 1.4.1:

  1. Decide where you want ant to be installed.
  2. Go to the following web site:

    http://jakarta.apache.org/builds/jakarta-ant/release/v1.4.1/bin

  3. Click on jakarta-ant-1.4.1-bin.zip and use the window that appears to indicate where you want the download to go.
  4. Go to the directory where you downloaded jakarta-ant-1.4.1-bin.zip. At the command line, type the following:

    unzip jakarta-ant-1.4.1-bin.zip

    This will create the directory jakarta-ant-1.4.1 containing all the unzipped files. You can delete the zip file once you have unzipped it.

  5. Set the environment variable ANT_HOME to the location of your ant installation.

To run some of the examples, you need the Tomcat 4.0.3 servlet engine. To install Tomcat 4.0.3:

  1. Decide where you want Tomcat to be installed.
  2. Go to the following web site:

    http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.0.3/bin

  3. Click on jakarta-tomcat-4.0.3.zip and use the window that appears to indicate where you want the download to go.
  4. Go to the directory where you downloaded jakarta-tomcat-4.0.3.zip. At the command line, type the following:

    unzip jakarta-tomcat-4.0.3.zip

    This will create the directory jakarta-tomcat-4.0.3 containing all the unzipped files. You can delete the zip file once you have unzipped it.

  5. Set the environment variable CATALINA_HOME to the location of your Tomcat installation.
Note: When you run the examples on Tomcat you must copy all the JAR files from the Java XML Pack to CATALINA_HOME/common/lib . Some of these files already exist in Tomcat distribution and should be overwritten by the Java XML Pack JARs. The xerces.jar that comes with the tomcat installation should also be removed from CATALINA_HOME/common/lib.

Modifying the Default Logging Level

At this release, the components of the Java XML Pack support the Jakarta Commons Logging API. The following levels are available, in ascending order of granularity:

fatal
error
warn
info
debug
trace

You can change the default level of logging for Tomcat. For example, to change the default level to debug, specify the following options (all on one line) in the CATALINA_OPTS environment variable definition. On Unix, you can use the "\" line continuation character in shell scripts to spread this over more than one physical line.

Unix: export CATALINA_OPTS="-Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.SimpleLog -Dorg.apache.commons.logging.simplelog.defaultlog=debug"

Microsoft Windows: set CATALINA_OPTS=-Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.SimpleLog -Dorg.apache.commons.logging.simplelog.defaultlog=debug

On UNIX systems, logging output appears in the file TOMCAT_HOME/logs/catalina.out.

On Microsoft Windows systems, logging output appears in the Tomcat window.

The default logger, SimpleLog, assumes that logger names are hierarchical. To set a default log level for all the technologies with package names beginning with com.sun.xml, you can say:

-Dorg.apache.commons.logging.log.com.sun.xml=info

For more information about configuring logging, see the Jakarta Commons Logging API documentation. In particular, refer to the Package Description.