org.apache.xml.resolver Release Notes

Version 1.1 CVS

Norman Walsh

Staff Engineer
Sun Microsystems, XML Technology Center

$Id$

6 September 2003


Table of Contents

The CatalogManager Is No Longer Static
System Catalogs Are Always Loaded
Tests/Examples Available
Bootstrap resolver for loading catalog files

This document offers a brief summary of what has changed in the Apache XML Commons Resolver package since the 1.0 release.

The most pervasive change is that the CatalogManager class is no longer static. It's now possible to instantiate several catalog managers and each manager can manage several catalogs.

There is still a single static instance of the CatalogManager, available via getStaticManager(). This is used by default if no other catalog manager is instantiated and used. It behaves as the old static one used to.

In the previous version, the system catalogs were not loaded if a private catalog was requested. That has changed; the system catalogs are now always loaded.

If you want to avoid loading any system catalogs, establish your own CatalogManager and use the setCatalogsFiles() method to assure that no system catalogs are available.

There are several tests in the tests/resolver directory that demonstrate how different instantiations can be used.

The resolver now includes catalog.{dtd,rng,xsd} and uses a "bootstrap" resolver when it is loading catalog files. This avoids the Catch-22 of having to resolve this before the resolver is in action ...

<!DOCTYPE catalog PUBLIC "-//OASIS//DTD XML Catalogs V1.0//EN"
"http://www.oasis-open.org/committees/entity/release/1.0/catalog.dtd">
<catalog>
<public publicId="foo" uri="bar"/>
</catalog>