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=7249>. 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=7249 DOMResult and StreamResult are not populated equally ------- Additional Comments From [EMAIL PROTECTED] 2002-03-19 16:11 ------- Known issue. The problem is that the DOM doesn't permit attaching a DocumentType to a Document after the latter has been created. That means we really can't fix it for DOMResults created using DOMResult(Node node) or DOMResult(Node node, java.lang.String systemID) -- just as we can't output an ill-formed document into a DOM, though SAX permits us to do so. The main difference is that the ill-formed case fails noisily, while we attempt to proceed past this one. We could, and should, alter our code so DOMResults created using the no-arguments constructor can include the DocumentType node. And I think we should request that JAXP add a DOMResult constructor that takes a DOMImplementation object as its parameter, so folks could get that behavior when outputting to a specific DOM implementation. After that's done, we should reconsider whether trying to output a DOCTYPE to an already-existing Document should be announced as an error, and if so what severity it should be assigned. Whether these changes are best considered a major bug, or an enhancement, may be open to debate... but it's definitely worth logging this into Bugzilla. Thanks for reminding us!
