JAXP default implementation and JDK-8152063

Alan Bateman Alan.Bateman at oracle.com
Mon Mar 21 18:38:45 UTC 2016

On 21/03/2016 14:39, David M. Lloyd wrote:
> This message is in reference to the aforementioned issue [1] that I've 
> requested my colleague Andrew Hughes to open on my behalf.
> As expressed in that issue, the means of specifying a JAXP default 
> provider (via system property which specifies a class name on the 
> application class path) is relatively antiquated at this point. It is 
> actually quite difficult for containers which ship their own JAXP 
> implementation to use the JDK APIs and, at the same time, ship their 
> own implementations, especially without polluting the class path of 
> applications which use JAXP.
It would be good to expand a bit on what you are looking to do.

Are you looking to change the system-wide default or are you looking for 
the container/app server to see a different default to the applications 
that it runs?

As things currently stand then then default can be overridden by 
deploying the XML parser on the class path or as a service provider 
module on the module path. The JPMS requirements document includes a 
requirement for ordering service providers that isn't implemented yet. 
If/when that happens then it might help with part of this.


More information about the core-libs-dev mailing list