Ni Nigel, You're right about the first issue, resolvePathThroughCatalogs does not resolve public IDs, so better try the solution suggested below: Indeed, the XMLUtilAccess.newNonValidatingXMLReader() returns an XML Reader which already has an entity resolver set up through the Oxygen catalogs. So as alternatives either you can use our XML Reader to parse resources or create an XML reader through our code and then do a XMLReader.getEntityResolver() on it to access the Entity Resolver set to it on our side. I will add as a feature request the possibility to get an EntityResolver or an URIResolver through our API. Regards, Radu Radu Coravu <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com On 10/29/2010 6:32 PM, Nigel Whitaker wrote:
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