Saxon

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.

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 Saxon Configuration to specify the catalogs used by Saxon.