On 08/08/2013 22:57, huizhe wang wrote:
Hi,
The root cause of this issue is that SPECJVM2008 uses a 3rd party
parser XOM 1.1 to convert the output to its canonical form. The XOM
parser directly references to the JDK parser implementation
"SAXParser" with a different configuration than the default JDK
parser, in this case, the DTD-only parser configuration
"DTDConfiguration". In JAXP 1.5, we added XMLSecurityPropertyManager
that is instantiated in the default configuration
"XML11Configuration". Since XMLSecurityPropertyManager is not
supported by DTDConfiguration, XOM no longer works.
I see this has been pushed but just so I understand, but can you expand
on what you mean by "directly references JDK parser implementation"? I'm
just wondering whether it's using the standard provider interfaces when
on the class path or whether it's tied to an old Xerces interface?
-Alan.
