Bug #5900
closedSaxon forces the catalog resolver's list of catalogs to be empty
100%
Description
When we create a CatalogResourceResolver
, we initialize the underlying resolver with an explicitly empty catalog list. This has the effect that any attempt by the user to specify a list of catalogs using system properties or a properties file will be ignored.
I think that's a bug. I think we should allow the user's environment to configure the catalog list (we let it configure all the other catalog properties).
Updated by Norm Tovey-Walsh about 1 year ago
Bah. Except we did it on purpose.
// We explicitly pass in an empty list so that in the absence of any other configuration, // the resolver doesn't use ./catalog.xml as a default. Historically, Saxon didn't use a // resolver unless a catalog was specified, so this default could have unexpected consequences.
I guess I'll just try to improve the documentation.
Updated by Norm Tovey-Walsh about 1 year ago
I propose we add the following paragraph to the docs:
Note: Saxon configures the resolver with an explicitly empty list of catalog files and does not use catalog files configured with properties or property files. This is a compromise for backwards compatibility because, historically, Saxon only used a catalog resolver if an explicit
-catalog
option was specified on the command line. If Saxon configured the resolver to use the global configuration, then it would always attempt to load./catalog.xml
as a catalog file and that could change the behavior of existing applications. You must use the-catalog
option or settings local to the SaxonConfiguration
to specify the catalogs used by Saxon.
Updated by Norm Tovey-Walsh about 1 year ago
- Status changed from New to Resolved
- Fix Committed on Branch 11, 12, trunk added
Resolved on 11, 12, and main by documenting the constraint more explicitly.
Updated by Debbie Lockett about 1 year ago
- Category set to Documentation
- Applies to branch 11, 12, trunk added
I have updated the Saxon 11 documentation online (XML and HTML versions). The Saxon 12 documentation will be updated with the next maintenance release.
Updated by O'Neil Delpratt about 1 year ago
- Status changed from Resolved to Closed
- % Done changed from 0 to 100
- Fixed in Maintenance Release 12.1 added
Bug fix applied in the Saxon 12.1 maintenance release.
Please register to edit this issue