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 bu...@apache.org on 2003/09/23 10:26:49 UTC

DO NOT REPLY [Bug 23345] New: - RFE: Allow to set org.apache.xerces.xni.parser.XMLParserConfiguration by JAXP

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23345>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23345

RFE: Allow to set org.apache.xerces.xni.parser.XMLParserConfiguration by JAXP

           Summary: RFE: Allow to set
                    org.apache.xerces.xni.parser.XMLParserConfiguration by
                    JAXP
           Product: Xerces2-J
           Version: 2.5.0
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: JAXP
        AssignedTo: xerces-j-dev@xml.apache.org
        ReportedBy: extern.thomas.pasch@volkswagen.de


Even if you use JAXP, it would be nice to get parsers with and without grammar 
caching. This is impossible to archive at the moment because grammar caching is 
triggered by setting a system property when using JAXP as pointed out by 
http://xml.apache.org/xerces2-j/faq-grammars.html . I suggest to add this 
feature to javax.xml.parsers.SAXParser.setProperty(String, Object) and to 
javax.xml.parsers.DocumentBuilderFactory.setAttribute(String, Object) (or more 
precisely the concrete classes that implements this in Xerces).

Perhaps a more general solution like the possiblity to pass a 
org.apache.xerces.xni.parser.XMLParserConfiguration to JAXP should be 
considered.

---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org