DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13193>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13193 Multiple xsd:imports on the same namespace Summary: Multiple xsd:imports on the same namespace Product: Xerces2-J Version: 2.2.0 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: XML Schema Structures AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] See bug 13191 against Xerces-C++ (and its attendent attachment). This message is a paste of that bug report: We have seen some schemas where the definition of a namespace is split between several schemas, each defining a subset of the namespace. An example of what I mean is attached: schemaA.xsd defines namespaceA, and imports both schemaB.xsd and schemaC.xsd into namespaceB. It then defines an element of each of the types defined in schemas B and C, in namespaceB. It appears that xerces ignores the second import, so the type defined in schemaC.xsd is not available when it is used to define the element. XMLspy, however accepts this use, and validates the instance fine. Also, the IBM XML Schema quality checker[1], claims there is no error in schemaA.xsd. As schemas and namespaces get larger, and more complicated, I expect this sort of separation to become more and more widespread. David [1] http://www.alphaworks.ibm.com/tech/xmlsqc --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
