A change committed some time between b09 and b12 added a security
feature in Xerces. This enforces a limit of 5000 on the maxOccurs
attribute of a xsd:sequence element. I asssume this is in order to
prevent a DOS attack on the VM from XML downloaded from the Internet.
However, it also enforces the limit when running the commend-line XJC
tool, and this causes a huge number of JCK failures.
This fix disables the SecurityManager, and so removes the limit, when
we're using the XJC tool.
Andrew.
2008-10-22 Andrew Haley <aph at redhat.com>
* patches/icedtea-xjc.patch: New.
--- openjdk/jaxws/src/share/classes/com/sun/tools/internal/xjc/reader/xmlschema/parser/SchemaConstraintChecker.java.prev 2008-10-21 15:50:20.000000000 +0100
+++ openjdk/jaxws/src/share/classes/com/sun/tools/internal/xjc/reader/xmlschema/parser/SchemaConstraintChecker.java 2008-10-21 15:57:37.000000000 +0100
@@ -66,6 +66,14 @@
SchemaFactory sf = SchemaFactory.newInstance(W3C_XML_SCHEMA_NS_URI);
sf.setErrorHandler(errorFilter);
+ try {
+ // By default the SchemaFactory imposes a limit of 5000 on
+ // xsd:sequence maxOccurs if a SecurityManager is
+ // installed. This breaks the specification of xjc,
+ // causing TCK failures.
+ sf.setProperty("http://apache.org/xml/properties/security-manager", null);
+ } catch (SAXException e) {
+ }
if( entityResolver != null ) {
sf.setResourceResolver(new LSResourceResolver() {
public LSInput resolveResource(String type, String namespaceURI, String publicId, String systemId, String baseURI) {