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=17979>. 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=17979 Transformations using DOMSource apply templates differently than with StreamSource ------- Additional Comments From [EMAIL PROTECTED] 2003-03-14 17:39 ------- Thanks for the workaround. I think bugs 12270 and 4995 may be related to this one. Bug 12270 appears to be having the same issue (although it is masked by the fact that the reporter is viewing output in a browser instead of directly), the reporter is using a similar tactic to obtain the DOMSource and seems to be encountering the same non-matching behavior. Bug 4995 seems to indicate something similar to this response. It indicates (correctly) that the XSLT is supposed to refer to the root of the DOM tree, and the DTM seems to make that attempt, but since it wasn't passed the Document node initially, it didn't set it's internal Document attribute properly. I suspect that this is a bug in how the DTM sets the Document attribute of the DTM when the DOMSource is initialized with a descendent node. The simplest solution might be to check if the input Node is a Document, and if it isn't, then call getOwnerDocument() to get the document root. Just a thought...
