You are viewing a plain text version of this content. The canonical link for it is here.
Posted to j-dev@xerces.apache.org by "Michael Glavassevich (JIRA)" <xe...@xml.apache.org> on 2006/05/06 21:00:21 UTC
[jira] Resolved: (XERCESJ-1158) Entity resolver is not applied to
namespace URI when used as possible Schema location
[ http://issues.apache.org/jira/browse/XERCESJ-1158?page=all ]
Michael Glavassevich resolved XERCESJ-1158:
-------------------------------------------
Resolution: Incomplete
I've discussed this with Andrew by e-mail. Since the DOM Level 3 and JAXP 1.3 APIs (supported by the latest versions of Xerces) can be used to do what you want I'm marking this issue resolved.
> Entity resolver is not applied to namespace URI when used as possible Schema location
> -------------------------------------------------------------------------------------
>
> Key: XERCESJ-1158
> URL: http://issues.apache.org/jira/browse/XERCESJ-1158
> Project: Xerces2-J
> Type: Bug
> Versions: 2.8.0
> Reporter: Anthony B. Coates
> Attachments: Correctly Resolving Schema Namespace URLs.doc
>
> When Xerces-J uses the namespace URI as a possible Schema location, it bypasses the entity resolver. This means that there is no way to resolve the Schema to a local copy when there is no explicit "schemaLocation". This is a major problem in enterprise scenarios where the schemaLocation in incoming XML messages may not be trustworthy, and only the namespace URI can be used to resolve the correct Schema for processing.
--
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: j-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-dev-help@xerces.apache.org