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 2001/11/26 11:40:41 UTC
DO NOT REPLY [Bug 5084] New: -
Effect of StandardParserConfiguration.setDocumentHandler
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=5084>.
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=5084
Effect of StandardParserConfiguration.setDocumentHandler
Summary: Effect of StandardParserConfiguration.setDocumentHandler
Product: Xerces2-J
Version: 2.0.0 [beta 2]
Platform: Other
OS/Version: Other
Status: NEW
Severity: Normal
Priority: Other
Component: XNI
AssignedTo: xerces-j-dev@xml.apache.org
ReportedBy: jjc@jclark.com
An XMLDocumentHandler registered by calling setDocumentHandler on a
org.apache.xerces.parsers.StandardParserConfiguration only gets called
if setDocumentHandler is called before setInputSource. This is very
surprising behaviour for anybody familiar with SAX, and there doesn't
seem to be any way to change document handlers during a parse. Is
there any reason why StandardParserConfiguration does not override
setDocumentHandler to install it in the last stage of the pipeline
public void setDocumentHandler(XMLDocumentHandler documentHandler) {
super.setDocumentHandler(documentHandler);
fNamespaceBinder.setDocumentHandler(fDocumentHandler);
}
?
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org