Hi Radu, Thanks for your quick answer. The catalog behaviour background info was very useful. We're still trying to work out the best way of using it:
Radu Coravu wrote: ... > > My suggestion for you is to use > XMLUtilAccess.resolvePathThroughCatalogs() because besides some very > little extra tests that's just what it does, it questions the > EntityResolver or the URIResolver (depending on the paramters it > receives) to resolve the reference. > > If we try to plug resolvePathThroughCatalogs into: InputSource org.xml.sax.EntityResolver.resolve(String publicId, String systemId) and then configure our parser with .setEntityResolver(), then wouldn't we be loosing the ability to do catalog resolving based on the publicId of editors/files? Alternatively, would the XMLUtilAccess.newNonValidatingXMLReader() method return an XMLReader already configured with the resolver and the framework/user/default catalogs you described? Thanks, Nigel -- Nigel Whitaker, DeltaXML: "Change control for XML" [email protected] http://www.deltaxml.com Registered in England: 02528681 Reg. Office: Monsell House, WR8 0QN, UK _______________________________________________ oXygen-user mailing list [email protected] http://www.oxygenxml.com/mailman/listinfo/oxygen-user
