JAXP default implementation and JDK-8152063
huizhe.wang at oracle.com
Thu Mar 24 20:54:50 UTC 2016
In this discussion so far,
a) I see that you seemed to have successfully used the method with a
class loader as Daniel suggested. I assume that solved the issue
reported in JDK-8152063. Am I right, that you no longer have issue with
using a proxy? Or
b) you do need JAXP's supporting using a Layer as the context in order
to solve your issue completely?
c) On org.xml.sax.helpers.XMLReaderFactory, as Alan and Daniel said, yes
I'm working with the SAX project to hopefully get a new release out that
would conform to the ServiceLoader spec. I'm also suggesting a new
method that takes a ClassLoader that would be useful if (a) worked for you.
On 3/24/2016 9:57 AM, Alan Bateman wrote:
> On 24/03/2016 14:57, David M. Lloyd wrote:
>> Does this mean that there will be a difference between upgradeable
>> modules and endorsed APIs under Jigsaw, or will all of JAXP be
>> fixed/locked to the platform including this API?
> It's not clear that it's feasible to separate the endorsed APIs from
> JAXP. Joe Wang looked into this a number of times. In practical terms
> then it's not clear that it would even be worth it as the W3C and SAX
> APIs are no longer evolving quickly. So to answer your question, they
> aren't upgradeable.
More information about the core-libs-dev