Explicit factory registration to avoid Services auto-discovery

I've experienced problems with the classloader-based validation back end
and datatype library autodiscovery mechanism.

 1) Right now, I'm experiencing a problem with the Schematron back end
failing to be auto-discovered on Windows (Java 5 and 6) while it works on
Mac (Java 5).
 2) Datatype library auto-discovery didn't work right with Java 6 on Mac
(works with Java 5 on Mac and OpenJDK 6 on Ubuntu).
 3) My attempts to set a security manager to restrict file system access
broke datatype library auto-discovery.

The classloader-based autodiscovery makes sense for the binary distribution
of the command-line tool, but it’s a pain for a larger app that provides a
closed set of jars anyway.

It would be useful to have an API for turning off the auto-discovery and to
have explicit registration methods for the different factories (e.g. a
method taking a DatatypeLibraryFactory instance for registering a datatype
library).

Original issue reported on code.google.com by hsivonen@iki.fi on 11 Nov 2008 at 8:15

qiuwei / jing-trang

Explicit factory registration to avoid Services auto-discovery #48