|
If you were logged in you would be able to see more operations.
|
|
|
|
File Attachments:
|
| |
Size |
|
acme.xsd |
2005-01-26 09:26 PM |
Lucian Holland |
0.5 kB |
|
|
Environment:
|
java 1.4 running on linux
|
|
| Resolution Date: |
28/Jan/05 05:59 AM
|
|
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.
|
|
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. |
Show » |
|
Bug
Closed
Minor
Target namespaces containing a space cause spurious errors
