Re: [Xerces 1.2.3][patch] EntityResolver not correctly tranmitted to TraverseSchema object

[ne...@ca.ibm.com]

Hi folks,

I think Sebastian's patch is right, and to help move this along I've
created a diff that will make committing it easier.  Could someone handle
this?
(See attached file: TraverseSchema-patch.txt)
Thanks,
Neil

Neil Graham
XML Parser Development
IBM Toronto Lab
Phone:  416-448-3519, T/L 778-3519
E-mail:  neilg@ca.ibm.com



Sebastien Sahuc <ss...@imediation.com> on 12/19/2000 05:14:30 AM

Please respond to xerces-j-dev@xml.apache.org

To:   xerces-j-dev@xml.apache.org
cc:
Subject:  [Xerces 1.2.3][patch] EntityResolver not correctly tranmitted to
      TraverseSchema object


I'm reposting it, since it hasn't got fixed in current CVS branch. Could
someone commit it  ?


Thanks,


[Xerces 1.2.3[patch] EntityResolver not correctly tranmitted to
TraverseSchema object


Indeed in the file
'org/apache/xerces/validators/schema/TraverseSchema.java', at line 1025
( method 'private void traverseImport(Element importDecl)' )


You should replace the line :
new TraverseSchema(root, fStringPool, importedGrammar, fGrammarResolver,
fErrorReporter, location);


with :
new TraverseSchema(root, fStringPool, importedGrammar, fGrammarResolver,
fErrorReporter, location, fEntityResolver);


That way the EntityResolver is correctly transmitted in the case when
'A.xsd' imports 'B.xsd' which in turn imports 'C.xsd', otherwise we end up
with an error message stating that the file 'C.xsd' couldn't be found in
the JVM working directory (din't build the C.xsd URL from the B.xsd URL)


All the best,


Sebastien

Re: [Xerces 1.2.3][patch] EntityResolver not correctly tranmitted toTraverseSchema object

[Arnaud Le Hors <le...@us.ibm.com>]

Committed. Thanks guys.
-- 
Arnaud  Le Hors - IBM Cupertino, XML Technology Group