org.apache.xml.resolver Release Notes Version 1.1 CVS 13 Nov 2002 $Id$ NormanWalsh Staff Engineer Sun Microsystems, XML Technology Center Sun Microsystems supports Norm's active participation in a number of standards efforts worldwide, including the Technical Architecture Group, XML Core, and XSL Working Groups of the World Wide Web Consortium, the OASIS RELAX NG Committee, the Entity Resolution Committee, for which he is the editor, and the DocBook Technical Committee, which he chairs. 2002 The Apache Software Foundation. This document offers a brief summary of what has changed in the Resolver package since the 1.0 release. I expect it'll be updated a few times before the next release.
The <classname>CatalogManager</classname> Is No Longer Static 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.
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 own CatalogManager and use the setCatalogsFiles() 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.