Saxon

It's unfortunately quite common for applications to use the JAXP factory mechanism to search for an XPath or XSLT implementation, and then rely on behaviour that isn't guaranteed to be common across implementations. There's not much we can do about this other than abandoning support for JAXP, which would hurt more users than it helps.

Rather than removing these files from the services metadata, a better approach is to set the relevant system properties (such as javax.xml.transform.TransformerFactory) to force loading of a JAXP implementation that the application is known to work with, e.g. the one that comes with the JDK.

Thanks Michael. Your solution is clearly cleaner.