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 2007/02/18 21:29:05 UTC

[jira] Resolved: (XERCESJ-1218) Composite key does not work

     [ https://issues.apache.org/jira/browse/XERCESJ-1218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Glavassevich resolved XERCESJ-1218.
-------------------------------------------

    Resolution: Fixed

The e2/@a2 field matches multiple times within the scope of the matched selector.  This is the error that Xerces was failing to detect.  It stopped matching the field XPath for each e1 after it found the first instance of e2/@a2.  I just committed a fix to SVN.  Can you please verify?  Thanks.

> Composite key does not work
> ---------------------------
>
>                 Key: XERCESJ-1218
>                 URL: https://issues.apache.org/jira/browse/XERCESJ-1218
>             Project: Xerces2-J
>          Issue Type: Bug
>          Components: XML Schema Structures
>    Affects Versions: 2.9.0
>            Reporter: Sorin Ristache
>         Assigned To: Michael Glavassevich
>         Attachments: keyConstraints.xml, keyConstraints.xsd
>
>
> In the attached sample schema the identity constraint set with the key named "checkAttrib" is not checked when the attached XML instance is validated against the sample schema. The validation should fail because there are elements e1 fo which the pair (@a1, e2/@a2) has duplicate values. The XML Schema specification say that the key is declared correctly.

-- 
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