You are viewing a plain text version of this content. The canonical link for it is here.
Posted to xml-commons-dev@xerces.apache.org by "Michael Glavassevich (JIRA)" <ji...@apache.org> on 2010/12/07 04:39:15 UTC
[jira] Updated: (XMLCOMMONS-50) No access to set parser features in
CatalogResolver
[ https://issues.apache.org/jira/browse/XMLCOMMONS-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Glavassevich updated XMLCOMMONS-50:
-------------------------------------------
Fix Version/s: XML Commons Resolver 1.2.0
> No access to set parser features in CatalogResolver
> ---------------------------------------------------
>
> Key: XMLCOMMONS-50
> URL: https://issues.apache.org/jira/browse/XMLCOMMONS-50
> Project: XmlCommons
> Issue Type: Bug
> Components: XML Commons Resolver (resolver.jar)
> Affects Versions: 1.x
> Environment: Operating System: All
> Platform: All
> Reporter: Mircea Enachescu
> Assignee: Commons Developers Mailing List
> Fix For: XML Commons Resolver 1.2.0
>
>
> Starting with the 1.2 resolver.jar the CatalogResolver on "resolve(String href,
> String base)" creates a parser for the SAXSource in order to set itself as an
> entity resolver to it. Unfortunately there is no external access to set the
> parser's features. For example, running an XPath over files with xincluded
> fragments fails because the XInclude feature is not set to that particular parser.
> Could there be some API provided so that the parser features could be set
> externally, or make creating the parser a protected method?
> Thanks, Mircea.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: xml-commons-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: xml-commons-dev-help@xerces.apache.org