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=4808>. 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=4808 using object identity as a substitute for isSameNode is bad idea ------- Additional Comments From [EMAIL PROTECTED] 2001-11-12 07:29 ------- The thing is that with "==" xalan can not be used with DOM implementations which do not comply. This is a big issue, especially with Java 1.4 comming with xalan integrated right in rt.jar. Maybe xalan should provide ability to subclass DOM2DTM class to make it possible to adjust it's behaviour? Or even better to provide version of DOMSource() constructor which accept some sort of comparator object? Using reflection to detect the fact that isSameNode is implemented is not a bad idea. It could be done once during first invocation so performance impact could be minimal. And what about Node.isSupported()? Could it be used to detect the fact that isSameNode implemented?
