org.apache.xml.resolver Release Notes (original) (raw)

Version 1.2

November 2006

Table of Contents

Apache XML Commons Resolver v1.2

Apache XML Commons Resolver v1.1

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 theApache XML Commons Resolverpackage. For further information, refer to the commons-dev and commons-cvs mailing lists and the Changes notes.

Apache XML Commons Resolver v1.2

The resolver now supports systemIdSuffix and uriSuffix as defined in the XML Catalogs v1.1 Committee Specification.

XCatalog support (Bugzilla Issue: 38562)

Fixed several bugs including one involving the use of "file: URLs".

Apache XML Commons Resolver v1.1

The `CatalogManager` Is No Longer Static

The most pervasive change is that the CatalogManagerclass 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 theCatalogManager, available viagetStaticManager(). This is used by default if no other catalog manager is instantiated and used. It behaves as the old static one used to.

System Catalogs Are Always Loaded

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 ownCatalogManager and use thesetCatalogsFiles() method to assure that no system catalogs are available.

Tests/Examples Available

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

Bootstrap resolver for loading catalog files

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 ...