[
https://issues.apache.org/jira/browse/XERCESJ-1205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12621259#action_12621259
]
Dannes Wessels commented on XERCESJ-1205:
-----------------------------------------
I encountered the same issue during the development of the exist-db project.
For performance reasons we cache the SAX parser and use the XMLGrammarPoolImpl
object. Example code for triggering the issue can be found here
http://existdb-contrib.googlecode.com/svn/trunk/XercesGrammarCache/ in
src/grammarcache ; I guess I need to to some cleanup here.
anyway, my get around for the moment is to remove all cached DTDs from the pool
when the reader is returned to the pool. A parser.reset() does not help either.
> Entity resolution does not work with DTD grammar caching resolved
> -----------------------------------------------------------------
>
> Key: XERCESJ-1205
> URL: https://issues.apache.org/jira/browse/XERCESJ-1205
> Project: Xerces2-J
> Issue Type: Bug
> Components: DTD
> Affects Versions: 2.8.1
> Environment: JDK1.5. The issue appears on various machines, Windows,
> Linux, Mac OSX. I don't believe it is platform specific.
> Reporter: Tin Pavlinic
> Attachments: bug.zip
>
>
> We have a DTD which defines some entities. We are parsing multiple documents
> against this DTD. If grammar caching is enabled, the entities are unresolved
> when the grammar is loaded from the cache, instead of the DTD.
> It seems that they are cleared every time a document is parsed and are only
> loaded when a DTD is loaded and not from the cache.
--
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]
