Bug #3725
closed
Diagnostics from Apache catalog resolver
Applies to branch:
9.8, trunk
Fix Committed on Branch:
9.8, trunk
Fixed in Maintenance Release:
Description
When the -t option is set on the command line, in conjunction with the -catalog option, Saxon sets the debug/verbosity level to 2, even if it has already been set externally to a higher value (using the system property xml.catalog.verbosity).
- Status changed from New to Resolved
- Applies to branch 9.8, trunk added
- Fix Committed on Branch 9.8, trunk added
Changed the relevant code in XmlCatalogResolver from
CatalogManager.getStaticManager().setVerbosity(2);
to
if (CatalogManager.getStaticManager().getVerbosity() < 2) {
CatalogManager.getStaticManager().setVerbosity(2);
}
Reopening this.
It seems that when the catalog does not exist, this is reported as a level 3 message to the application's Debug object. By setting the default verbosity to 2 (when -t is specified) (or to 0 otherwise), no messages are being output and execution falls back silently to not using the catalog.
I have added code to CommandLineOptions.java to test, in the case where -catalog is a file and not a URI, that the file actually exists, and to throw a hard error if not, before we even pass it to the resolver. You'll still get the existing behaviour if the value of -catalog is a URI.
- Status changed from Resolved to Closed
- % Done changed from 0 to 100
- Fixed in Maintenance Release 9.8.0.12 added
Bug fix applied in the Saxon 9.8.0.12 maintenance release.
Please register to edit this issue
Also available in: Atom
PDF
.