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=6258>. 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=6258 Relative references to files lead to missing, duplication definitions. Summary: Relative references to files lead to missing, duplication definitions. Product: Xerces2-J Version: 2.0.0 Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Critical Priority: Other Component: XML Schema Structures AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] I have identified a situation in 2.0.0 whereby relative file paths are not processed correctly for imports/includes, resulting in both the non-loading of files, e.g., [Error] StarProcessPurchaseOrder.xml:6:366: src-resolve: Cannot resolve the name 'oa:Line' to a(n) elment declaration component. and the reporting of large numbers of duplicate global elements, e.g., sch-props-correct.2: a schema cannot contain two global components with the same name; this one contains two occurrences of 'http://www.openapplications.org/oagis,EmployeeId'. These appear to occur when there are two different relative references to the same file, especially when there is use of "../" in the path. While this practice is not necessarily a good one, it is sometimes unavoidable. I'm guessing that the problem either has something to do with imports versus includes, or that it has something to do with keeping track of (and comparing) relative references rather than resolving (and comparing) the absolute file paths. Specifically, we have two schema sets in sibling directories: /ABC/OAGIS /ABC/Overlays Several files in the OAGIS hierarchy *include* other files within the OAGIS hierarchy, using relative references, e.g., ../Resources/Components.xsd This works fine. Similarly, when the files in the Overlays include other files in Overlays (using relative references), there are no problems It breaks down is when files in the Overlays hierarchy build on files in the OAGIS hierarchy, specifically by *importing* from the OAGIS hierarchy: ../../../OAGIS/Resources/Components.xsd Interestingly, when the imports use absolute file path references, these errors disappear, even in all of the includes (in both namespaces) continue to use relative references. It could be that imports and includes use different means of determining whether the file has already been visited. This is a real showstopper for us; we need this to work in order for us to release OAGIS 8, the schema version of the Open Applications Group Integration Specification (http://www.openapplications.org). Thanks, Mark Feblowitz XML Architect, Frictionless Commerce and OAGI --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
