I guess what Armin and I were saying is that the included schema should be able to be referenced by the original schema by a relative path extending from the original schema. If you reference all schemas relative to your XML file, then when you open your original schema (which is in a seperate directory than your XML file) in say, XML Spy, then it can't find the included schema. Also, it doesn't appear to be the case that XERCES 1.4.1 is looking for the schema in the prog executing directory. Try to parse Armin's XML file in a seperate directory from your execution directory and you will get an error XSD not found in the XML file's directory.
-David -----Original Message----- From: Etienne Roy [mailto:[EMAIL PROTECTED] Sent: Thursday, July 19, 2001 10:26 AM To: [EMAIL PROTECTED] Subject: Re: Schema not found Armin, Xerces look up the files relatively to the directory you're runnning your prog in, and not the one your first schema is: > > [Warning] :0:0: File "file:///home/dave/tmp/ML_primitive.xsd" not found. Your prog in running in home/dave/tmp/ where it's looking for ML_primitive, that is not here but in xsd/. If you change <include schemaLocation="ML_primitive.xsd"/> to <include schemaLocation="xsd/ML_primitive.xsd"/> in ML.xsd, that works. Same thing if you move both schemas in tmp/ and remove the relative path in your instance. > I have a schema which includes another schema. Xerces doesn't find the > included schema, if the schema files and the xml file are in different > directories. What can I do? I know I asked the same question a few days ago, > but there was no answer. I really need a solution to the problem. Cheers -- Etienne --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
