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.

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|INVALID                     |



------- Additional Comments From [EMAIL PROTECTED]  2002-02-07 17:21 -------
I'm reopening this because, using the 06-Feb-02 13:12 jars, it is still a 
critical problem for us.

I've simplified my code somewhat, and the errors I'm seeing are with 
recognizing relative references in imports, and resultant "src-resolve" errors:

    "src-resolve: Cannot resolve the name 'oa:PurchaseOrder' to a(n) type 
     definition component."

I'll look to see what change made the duplicate definitions go away.

I've attached a set of xsd and xml files that demonstrate part of the problem - 
the relative referencing in imports that do not seem to work. The places to 
look are in Overlays/Star/BODExamples/ProcessPurchaseOrder.xml and 
Overlays/StarABS/BODExamples/ProcessPurchaseOrder.xml. The first is the error 
case and the second is the ABSolute reference example where the errors are 
eliminated. 

In the former case, the xml file references its corresponding xsd file, which 
imports using relative references. This results in 3 "src-include.0: Failed to 
read included schema document" warnings and a series of "src-resolve" errors. 
In the latter case, the 3 imports are performed using absolute path names and 
these errors disappear.

The results of running the 06-Feb-02 13:12 jars is captured in "err.txt" in the 
respective folders.

I acknowledge that there are 4 remaining errors in the "ABS" case - these are 
legitimate schema errors that we must fix. I don't believe that these have any 
bearing on the import problems.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to