[
https://issues.apache.org/jira/browse/XERCESJ-797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Glavassevich resolved XERCESJ-797.
------------------------------------------
Resolution: Won't Fix
Assignee: (was: Xerces-J Developers Mailing List)
The reporter wanted to be able to control grammar caching per parser instance.
This was made possible in JAXP 1.3 with the introduction of the
javax.xml.validation API. It's been possible for even longer with the
XMLGrammarPool property. No need to introduce a new property.
> RFE: Allow to set org.apache.xerces.xni.parser.XMLParserConfiguration by JAXP
> -----------------------------------------------------------------------------
>
> Key: XERCESJ-797
> URL: https://issues.apache.org/jira/browse/XERCESJ-797
> Project: Xerces2-J
> Issue Type: Bug
> Components: JAXP (javax.xml.parsers)
> Affects Versions: 2.5.0
> Environment: Operating System: Other
> Platform: Other
> Reporter: Thomas Pasch
>
> 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.
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
