Arturo Perez wrote:
During one iteration I put the URIResolver on every XMLReader created by that codepath. Same problem. Is that different than what you/Jeremy suggested?
Probably, although putting an URIResolver on an XMLReader is, umm, difficult. Either you mean EntityResolver instead of URIResolver, which isn't (and can't) be used to resolve URIs in document() calls, or you mean other things like Transformer instead of XMLReader. Setting the custom URIResolver on the relevant Transformer objects would be the correct thing to do. J.Pietschmann --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
