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=7074>. 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=7074 Unwarranted error regarding "no circular definitions allowed" Summary: Unwarranted error regarding "no circular definitions allowed" Product: Xerces-C++ Version: 1.6.0 Platform: PC OS/Version: Linux Status: NEW Severity: Major Priority: Other Component: Validating Parser (Schema) (Xerces 1.5 or up only) AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Symptom: #SAX2Print -v=always -p test.xml <?xml version="1.0" encoding="LATIN1"?> Error at file test.xml, line 3, char 101 Message: No circular definitions are allowed: 'RecursiveGroup' To Reproduce: Run the attached sample document through ny of the *Print sample programs with schema validation turned on. The error occurs for RecursiveGroup. Source Of Problem: It seems that XercesC does not like a schema that utilizes two complexTypes of different names but the same content model. The first one is acceptable but the second one generates a "no circular definitions allowed" error if it is used as the type of an element. Analysis: I don't know the bowels of TraverseSchema well enough to say, but this seems to happen when TraverseSchema::processGroupRef is called with a "false" value for the circularAllowed argument (stack level 4). I have tried the sample program with both IBM's SQC (Schema Quality Checker) and Altova's XML Spy. both of those XML processors indicate that the attached schema is valid. I've also looked at the XML Schema spec (Part 0 & 1) and can't seem to find anything that would contradict such a schema specification. In large schemas, like the one I'm trying to build, it is often convenient to use groups to simply collect together groups of related elements. These groups are then combined into larger assemblies of groups. It appears that Xerces doesn't like this much. Version Note: This problem has been identified on both 1.6.0 and 1.7.0 but not any earlier version. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
