-
Bug
-
Resolution: Won't Fix
-
P3
-
7
-
generic
-
generic
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2206350 | 7 | Joe Wang | P3 | Closed | Won't Fix |
There is wrong result in an JCK negative testing: attached schematas are valid, although it was expected the opposite.
It contradicts to the specification http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/structures.html#element-schema) that states:
Since the empty string is not a legal namespace name, supplying an empty string for targetNamespace is incoherent, and is not the same as not specifying it at all. The appropriate form of schema document corresponding to a ·schema· whose components have no {target namespace} is one which has no targetNamespace attribute specified at all.
It contradicts to the specification http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/structures.html#element-schema) that states:
Since the empty string is not a legal namespace name, supplying an empty string for targetNamespace is incoherent, and is not the same as not specifying it at all. The appropriate form of schema document corresponding to a ·schema· whose components have no {target namespace} is one which has no targetNamespace attribute specified at all.
- backported by
-
JDK-2206350 Empty string value of namespace and targetNamespace attributes is allowed by schema parser
-
- Closed
-