[ http://issues.apache.org/jira/browse/XERCESJ-1104?page=comments#action_12332090 ]
Michael Glavassevich commented on XERCESJ-1104: ----------------------------------------------- What XMLCatalogResolver does is documented both in the Javadoc and in the documentation which accompanies Xerces. It was discussed and reviewed with the community when it was under development. It does what it says it does and has been that way for almost two years now. We cannot change what the methods do without breaking existing users. During the initial discussion on the lists and elsewhere it became pretty evident that no one implementation of the resolveEntity() methods will meet the requirements of all applications, so we went with fairly generalized default behaviour which may or may not do the right thing for your application. This is why the Javadoc clearly states that the methods should be overrided in a subclass if you want them to do something else. > 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]
