[jira] Updated: (XERCERJ-156) Relative references to files lead to missing, duplication definitions.

[ji...@apache.org]

The following issue has been updated:

    Updater: Serge Knystautas (mailto:sergek@lokitech.com)
       Date: Mon, 12 Apr 2004 2:17 PM
    Changes:
             Attachment changed from OAGIS 8.0 020602-00-mdf.zip
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://issues.apache.org/jira/browse/XERCERJ-156?page=history

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/XERCERJ-156

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: XERCERJ-156
    Summary: Relative references to files lead to missing, duplication definitions.
       Type: Bug

     Status: Resolved
 Resolution: FIXED

    Project: Xerces2-J

   Assignee: Xerces-J Developers Mailing List
   Reporter: Mark Feblowitz

    Created: Wed, 6 Feb 2002 12:53 AM
    Updated: Mon, 12 Apr 2004 2:17 PM
Environment: Operating System: Windows NT/2K
Platform: PC

Description:
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


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org