[ http://issues.apache.org/jira/browse/XERCESJ-1104?page=comments#action_12331625 ]
Michael Glavassevich commented on XERCESJ-1104: ----------------------------------------------- If you understood what I described I was hoping you would have realized that the single method on XMLEntityResolver works for any kind of resource. Both the method parameter (XMLResourceIdentifier) and return type (XMLInputSource) are extensible. Heck you can even return DOM nodes and SAX parsers (see org.apache.xerces.util.DOMInputSource & org.apache.xerces.util.SAXInputSource) from this method. There's nothing you can't do with this method that would require another one, especially another method with essentially the same signature. I have a feeling you're just getting hung up on the name of the interface. XNI borrowed many concepts from SAX including the names of its classes, interfaces and methods; XMLEntityResolver being no exception. Perhaps it should have been called XMLResourceResolver since that's essentially what it is (but it's too late now). XMLEntityResolver evolved far beyond what SAX supports. Perhaps the Javadoc for XMLEntityResolver should be updated to reflect that it has the ability to resolve more than just XML parsed entities since this is how it's always been used. In my opinion that's the only thing that should be fixed here. > Resolution of schemaLocation URIs should be via URI resolution, not entity > resolution > ------------------------------------------------------------------------------------- > > Key: XERCESJ-1104 > URL: http://issues.apache.org/jira/browse/XERCESJ-1104 > Project: Xerces2-J > Type: Bug > Components: XNI > Versions: 2.6.0, 2.7.1 > Environment: All > Reporter: William Eliot Kimber > > The resolveSchema() method of XSDHandler uses the entityResolver to resolve > URIs in schema location hints. This has the effect that, when using a catalog > resolver that SYSTEM entries are used to resolve the schema URIs. > However, schemas are not entities and therefore their URI references should > not be resolved via an entity resolver but via a URI resolver and should, > therefore be resolved via URI catalog entries, not SYSTEM entries. > That is, by the OASIS Entity Resolution spec one would expect to declare URI > entries to remap schema location URIs but this does not work. > I'm happy to develop a fix but it may take me a while to figure out exactly > how to go about it. > Because this behavior has been around for a while (since at least version > 2.6) and is documented in at least one tutorial I found, it will probably be > necessary to control the use of an entityResolver or URI resolver through a > system property. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
