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/11/13 17:15:46 UTC
DO NOT REPLY [Bug 24669] -
Internal entities added via addInternalEntity() are lost
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=24669>.
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=24669
Internal entities added via addInternalEntity() are lost
mrglavas@apache.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |INVALID
------- Additional Comments From mrglavas@apache.org 2003-11-13 16:15 -------
This is working as designed. The table of entities in the XMLEntityManager
is transient. This table gets filled by the DTDScanner as it reads entity
declarations in the DTD. It gets dumped on reset to remove entities from the
previous parse.
If you want the parser to recognize arbitrary entities (which aren't declared
anywhere) then you should probably create your own parser configuration,
perhaps one which extends one of the Xerces configurations.
If you extended IntegratedParserConfiguration for instance, and overloaded
createEntityManager with your own extentsion of XMLEntityManager which you load
with some persistent predefined entities, you can achieve what you want. Just
be warned that these implementation classes may change between releases. If
you're comfortable with that, then this approach should work for you.
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org