You are viewing a plain text version of this content. The canonical link for it is here.
Posted to j-dev@xerces.apache.org by "Michael Glavassevich (JIRA)" <xe...@xml.apache.org> on 2011/01/24 17:29:44 UTC
[jira] Resolved: (XERCESJ-1492) maxOccurs checking broken in XML
Schema 1.1 beta distribution
[ https://issues.apache.org/jira/browse/XERCESJ-1492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Glavassevich resolved XERCESJ-1492.
-------------------------------------------
Resolution: Fixed
Fixed in SVN rev 1062852.
> maxOccurs checking broken in XML Schema 1.1 beta distribution
> -------------------------------------------------------------
>
> Key: XERCESJ-1492
> URL: https://issues.apache.org/jira/browse/XERCESJ-1492
> Project: Xerces2-J
> Issue Type: Bug
> Components: XML Schema 1.0 Structures, XML Schema 1.1 Structures
> Affects Versions: 2.11.0
> Reporter: Michael Glavassevich
>
> In the XML Schema 1.1 beta distribution of Xerces-J 2.11.0, the code for checking overflow of maxOccurs is incorrect. There's an index into a table which is off by one and that's allowing more instances to go through than should be allowed. We need to increment the index before entering the loop in XSDFACM.findMatchingDecl() so that we don't match the same declaration again.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: j-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-dev-help@xerces.apache.org