[ http://issues.apache.org/jira/browse/XERCESJ-1070?page=all ]
David Sheldon updated XERCESJ-1070:
-----------------------------------
Attachment: maxOccurs.patch
Patch to fix both of my suggestions here.
> Error when maxOccurs greater than that enforced by security manager is
> incorrect.
> ---------------------------------------------------------------------------------
>
> Key: XERCESJ-1070
> URL: http://issues.apache.org/jira/browse/XERCESJ-1070
> Project: Xerces2-J
> Type: Bug
> Components: XML Schema Structures
> Versions: 2.6.2
> Reporter: David Sheldon
> Priority: Minor
> Attachments: maxOccurs-total.xsd, maxOccurs.patch, maxOccurs1001.xsd
>
> We have enabled the security manager, limiting the number of maxOccurs to
> 3000.
> Xerces says
> "Current configuration of the parser doesn't allow a maxOccurs attribute value
> to be set greater than the value 3,000"
> This is misleading on two counts.
> 1. This error is reported if maxOccurs for a particular element is set to
> 1001 (not 3001).
> 2. It is also reported if the sum of the maxOccurs across many elements in
> the schema is
> greater than 1000.
> The first of these appears to be caused by inconsistancy in CMNodeFactory:
> private static final int MULTIPLICITY = 1 ;
> ...
> //we are setting the limit of number of nodes to 3times the maxOccur value..
> if(fSecurityManager != null){
> maxNodeLimit = fSecurityManager.getMaxOccurNodeLimit() * MULTIPLICITY ;
> }
> I'm guessing that MULTIPLICITY should be 3.
> The second of these will require rewording the error message. How about
> "Current configuration of the parser doesn't allow maxOccurs attribute values
> in a schema
> to sum to greater than 3,000."
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
|
Try Searching:
servers, voip, java, networking, microsoft ...
|
|
|
|