xml-commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 41101] New: - No access to set parser features in CatalogResolver
Date Mon, 04 Dec 2006 08:15:24 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=41101>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=41101

           Summary: No access to set parser features in CatalogResolver
           Product: XmlCommons
           Version: 1.x
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Resolver
        AssignedTo: commons-dev@xml.apache.org
        ReportedBy: mircea@sync.ro


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.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Mime
View raw message