You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@xerces.apache.org by "Boris Kolpackov (JIRA)" <xe...@xml.apache.org> on 2008/02/13 08:44:08 UTC
[jira] Created: (XERCESC-1777) Restriction checking code resolves
an element from a wrong schema grammar
Restriction checking code resolves an element from a wrong schema grammar
-------------------------------------------------------------------------
Key: XERCESC-1777
URL: https://issues.apache.org/jira/browse/XERCESC-1777
Project: Xerces-C++
Issue Type: Bug
Components: Validating Parser (Schema) (Xerces 1.5 or up only)
Affects Versions: 2.8.0
Environment: any
Reporter: Boris Kolpackov
Assignee: Boris Kolpackov
The attached test case demonstrates a bug in restriction handling logic. After some debugging it appears that the element in the base type is resolved in the wrong schema grammar. Normally it would fail and the fall back cases would resolve the corrent element. But in this test case we have an otherwise unrelated type at the right position which happened to have an element with the same. If one renames the Value element in the bar type, the error goes away.
--
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: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org
[jira] Updated: (XERCESC-1777) Restriction checking code resolves
an element from a wrong schema grammar
Posted by "Boris Kolpackov (JIRA)" <xe...@xml.apache.org>.
[ https://issues.apache.org/jira/browse/XERCESC-1777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Boris Kolpackov updated XERCESC-1777:
-------------------------------------
Attachment: test.xml
derived.xsd
base.xsd
> Restriction checking code resolves an element from a wrong schema grammar
> -------------------------------------------------------------------------
>
> Key: XERCESC-1777
> URL: https://issues.apache.org/jira/browse/XERCESC-1777
> Project: Xerces-C++
> Issue Type: Bug
> Components: Validating Parser (Schema) (Xerces 1.5 or up only)
> Affects Versions: 2.8.0
> Environment: any
> Reporter: Boris Kolpackov
> Assignee: Boris Kolpackov
> Attachments: base.xsd, derived.xsd, test.xml
>
>
> The attached test case demonstrates a bug in restriction handling logic. After some debugging it appears that the element in the base type is resolved in the wrong schema grammar. Normally it would fail and the fall back cases would resolve the corrent element. But in this test case we have an otherwise unrelated type at the right position which happened to have an element with the same. If one renames the Value element in the bar type, the error goes away.
--
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: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org
[jira] Resolved: (XERCESC-1777) Restriction checking code resolves
an element from a wrong schema grammar
Posted by "Boris Kolpackov (JIRA)" <xe...@xml.apache.org>.
[ https://issues.apache.org/jira/browse/XERCESC-1777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Boris Kolpackov resolved XERCESC-1777.
--------------------------------------
Resolution: Fixed
Fix Version/s: 3.0.0
Fixed in the trunk and xerces-2.
> Restriction checking code resolves an element from a wrong schema grammar
> -------------------------------------------------------------------------
>
> Key: XERCESC-1777
> URL: https://issues.apache.org/jira/browse/XERCESC-1777
> Project: Xerces-C++
> Issue Type: Bug
> Components: Validating Parser (Schema) (Xerces 1.5 or up only)
> Affects Versions: 2.8.0
> Environment: any
> Reporter: Boris Kolpackov
> Assignee: Boris Kolpackov
> Fix For: 3.0.0
>
> Attachments: base.xsd, derived.xsd, test.xml
>
>
> The attached test case demonstrates a bug in restriction handling logic. After some debugging it appears that the element in the base type is resolved in the wrong schema grammar. Normally it would fail and the fall back cases would resolve the corrent element. But in this test case we have an otherwise unrelated type at the right position which happened to have an element with the same. If one renames the Value element in the bar type, the error goes away.
--
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: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org
[jira] Closed: (XERCESC-1777) Restriction checking code resolves an
element from a wrong schema grammar
Posted by "Boris Kolpackov (JIRA)" <xe...@xml.apache.org>.
[ https://issues.apache.org/jira/browse/XERCESC-1777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Boris Kolpackov closed XERCESC-1777.
------------------------------------
> Restriction checking code resolves an element from a wrong schema grammar
> -------------------------------------------------------------------------
>
> Key: XERCESC-1777
> URL: https://issues.apache.org/jira/browse/XERCESC-1777
> Project: Xerces-C++
> Issue Type: Bug
> Components: Validating Parser (Schema) (Xerces 1.5 or up only)
> Affects Versions: 2.8.0
> Environment: any
> Reporter: Boris Kolpackov
> Assignee: Boris Kolpackov
> Fix For: 3.0.0
>
> Attachments: base.xsd, derived.xsd, test.xml
>
>
> The attached test case demonstrates a bug in restriction handling logic. After some debugging it appears that the element in the base type is resolved in the wrong schema grammar. Normally it would fail and the fall back cases would resolve the corrent element. But in this test case we have an otherwise unrelated type at the right position which happened to have an element with the same. If one renames the Value element in the bar type, the error goes away.
--
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: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org