Target namespaces containing a space cause spurious errors
----------------------------------------------------------
Key: XERCESJ-1039
URL: http://issues.apache.org/jira/browse/XERCESJ-1039
Project: Xerces2-J
Type: Bug
Components: XML Schema Structures
Versions: 2.6.2
Environment: java 1.4 running on linux
Reporter: Lucian Holland
Priority: Minor
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
