[ http://issues.apache.org/jira/browse/XERCESJ-1104?page=comments#action_12332632 ]
Norman Walsh commented on XERCESJ-1104: --------------------------------------- If the current "out of the box" configuration uses the EntityResolver in its attempt to locate a schema document for a schema URI, it is manifestly doing the wrong thing. The documentation for resolveEntity() is clear: Allow the application to resolve external entities. ... Application writers can use this method to redirect external system identifiers Whatever else may be true, neither namespace names nor schema location hints can properly be called "external identifiers". That said, I'm sympathetic to the position that says that XNI needs to have some flexibility at this level. Many applications support a command line option that allows the user to identify the name of a class to be used to instantiate an EntityResolver. Is there an analagous object in the XNI paradigm that could be instantiated and could applications reasonably be expected to support this behavior? I'd be happy to extend the XML Commons Resolver to support new interfaces to make proper use of XML Catalogs with Apache schema processing easier. > 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]
