[ 
https://issues.apache.org/jira/browse/XERCESC-1581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12608895#action_12608895
 ] 

Thom Bartold commented on XERCESC-1581:
---------------------------------------

This issue has still not been resolved in xerces-c version 2.8.0. It has 
apparently been resolved in xerces2-j 2.9.1. 

If this issue were resolved in 2.7.0, it should have been correct in version 
2.8.0.

> anyURI spaces rejected, while RFC allows them
> ---------------------------------------------
>
>                 Key: XERCESC-1581
>                 URL: https://issues.apache.org/jira/browse/XERCESC-1581
>             Project: Xerces-C++
>          Issue Type: Bug
>          Components: Validating Parser (XML Schema)
>    Affects Versions: 2.7.0
>         Environment: Windows XP, Linux, Mac OSX Tiger
>            Reporter: Chris Storah
>
> When validating an instance document based on a schema that uses the 
> xs:anyURI datatype, spaces cause a validation error to be thrown (and the 
> following message is displayed):
>    Message: Datatype error: Type:InvalidDatatypeValueException, Message:Value 
> 'urn:abc:v1 schema.xsd' is NOT a valid URI .
> Although the schema specification says spaces should be avoided, in this case 
> the document is coming from an external source so spaces are used.
> See http://www.w3.org/TR/xmlschema-2/#anyURI
> As the URI validation code calls XMLUri::isValidURI, the problem can be 
> emulated using the code: 
> XMLCh* test = X("urn:abc:v1 schema.xsd");     // fails
> //XMLCh* test = X("urn:abc:v1%20schema.xsd"); // works
> bool valid = XMLUri::isValidURI(true, test);
> Also, I notice that Xerces-J had a similar problem:
> http://issues.apache.org/bugzilla/show_bug.cgi?id=18785
> Is this a bug?
> If not, is there anyway around this problem - apart from replacing spaces 
> with their escaped versions prior to parsing?
> Chris

-- 
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to