[
https://issues.apache.org/jira/browse/XERCESJ-1518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13066856#comment-13066856
]
Chris Simmons commented on XERCESJ-1518:
----------------------------------------
Whilst the patch fixes the observed problem I doubt that its complete as
anything using the attribute name value directly is liable to be similarly
wrong so they all need review. Perhaps the correct fix is to refactor
everything using the SchemaSymbols.ATT_NAME to instead use the appropriate
validator (presumably the names are all of type xs:NCName) to construct an
object to use as a key instead. I think that this is effectively what happens
when there's a backwards reference.
> Forward references to types etc are not subject to whitespace normalization.
> ----------------------------------------------------------------------------
>
> Key: XERCESJ-1518
> URL: https://issues.apache.org/jira/browse/XERCESJ-1518
> Project: Xerces2-J
> Issue Type: Bug
> Components: XML Schema 1.0 Datatypes
> Affects Versions: 2.11.0
> Reporter: Chris Simmons
> Attachments: schema-whitespace-patch.txt
>
>
> If, say, an element references its type and the element is lexically before
> the type then the type may fail to resolve if the type name contains
> whitespace. This will happen for all cross references as they are handled
> similarly. I'll attach a patch with a test and simple fix shortly.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: j-dev-unsubscr...@xerces.apache.org
For additional commands, e-mail: j-dev-h...@xerces.apache.org
