... and the usual disclaimer. What ships in Java 5 is Sun's fork of the
Xerces codebase. It is not Xerces 2.6.2 or any other Apache version for
that matter. All sorts of changes and additions were made to it since it
branched from the Apache code that we are not aware of and have no
influence over
You can put any URI you want into the location attribute on import or
include, and resolve it from schemas held in strings or relational
databases or resources in a jar file or anything else, if you provide
an EntityResolver to the parser. See
DocumentBuilder.setEntityResolver().
You can also use
I have been made aware of a bug in Xerces 2.6.2 on JRE 1.5.0_18:
According to source code comments there is a bug in xerces that prevents
it from parsing schemas with imports and includes correctly:
Xerces (used by JAXP in Java 1.5 and later) does not correctly parse
composite schema,
(i.e. sche
