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=7761>. 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=7761 Child list of parsed entity is empty [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX ------- Additional Comments From [EMAIL PROTECTED] 2004-01-16 15:01 ------- There are two possible interpretations to "is available": 1) The entity replacement text is available (not null) in DTD 2) The parser has the replacement value available. In Xerces the parser has it available when entity was referenced in the document. I believe the spec. intention was (2). But given that some peope think the intention was (1) and that to my recollection no user ever asked this to be changed, I am marking this bug WON'T FIX. To explain why we are not planning to fix this bug, here is some additional information on how parser works: When parser sees declaration of the entity the parser does not parse the entity yet. This happens for several reasons: · The scanner that scans DTD can't scan XML document content, so if replacement text has element, e.g. "<p:foo>text</p:foo> which is supposed to be reported as element event, the DTD scanner can only handle it as text. · The replacement text might have namespace prefixes that can be only resolved when entity is placed in the document. · There are might be default attributes that will be added to the element (normally done by DTDValidator). Given above reasons (there might be more of those), Xerces will only parse the content of the entity when the entity is placed in the document, i.e. Xerces sends all the events down the pipeline and use those events to construct the replacement value of DOM Entity node. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
