Target namespaces containing a space cause spurious errors

• Key: XERCESJ-1039
• Type: Bug
• Status: Closed
• Resolution: Fixed
• Priority: Minor
• Assignee: Michael Glavassevich
• Reporter: Lucian Holland
• Component/s: XML Schema 1.0 Structures
• Affects Version/s: 2.6.2

Description

In a schema which has a space in the target namespace, references to other components in the schema fail. I believe that this is because the targetNamespace is escaped by the schema loader, but the corresponding prefix binding does not get escaped. As a result the parser thinks that the prefix refers to a different namespace to that of the current schema! The attached schema demonstrates this. Note that it works if you bind a prefix to a pre-escaped version of the namespace. Obviously namespaces containing unescaped spaces are not a great idea, but it would be helpful if Xerces was consistent in its behaviour and failed in a slightly more explicit fashion on this.

Comments

[Lucian Holland]

Schema that shows the problem.

[Michael Glavassevich]

To validate an anyURI we apply the escaping rules from XLink to make it a URI that we then validate with Xerces' URI class. We were returning the escaped value instead of the original as the actual value. This was affecting all anyURIs containing characters excluded by RFC 2396. Thanks for catching this. A fix is now in CVS.

[Lucian Holland]

Sorry - didn't get round to verifying this until now. All works fine now - thanks for the quick turnaround!