No deps on JAXP was: JDK support for VM to read classes from modules in a module library

Alan Bateman Alan.Bateman at oracle.com
Mon May 21 01:55:35 PDT 2012


On 18/05/2012 08:07, Jaroslav Tulach wrote:
> :
>
> Should you agree that elimination of java.base =>  JAXP linkage dependency is
> reasonable goal and you just don't want to bother with it now, I'd be happy to
> try it myself and prepare a patch.
>
Yes, I think we all agree that eliminating the base->jaxp dependency is 
a reasonable goal. The troublesome methods are (as you know) 
Properties.loadfromXML and storeToXML. It may be possible to just 
re-implement storeToXML so that it doesn't use JAXP. For loadFromXML 
then a long standing suggestion has been to relax its specification to 
allow it be implemented with a simple non-validating parser that can 
parse most properties files in XML format. Whether this eliminates or 
just reduces the need for JAXP isn't clear at this point but it would be 
really nice to just not require JAXP. As it stands then it's an optional 
dependency but not in a clean way (as we've been discussing on this 
thread) due to sun.util.xml.XMLUtils. So I think the right course of 
action on this one is to first explore whether we can eliminate the 
dependency completely, and if not then it brings us to the options that 
we are discussing on this thread. I would also throw in the pot the 
dependencies that JAX-WS and XML-DSIG have on internal JAXP clases as 
that will need to be tackled if JAXP is to be truely replaceable.

-Alan.





More information about the jigsaw-dev mailing list