DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=27963>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=27963 setAttribute duplicates an attribute with an empty value instead of replacing it ------- Additional Comments From [EMAIL PROTECTED] 2004-04-05 23:25 ------- The recommendation does say that the DOM-1 and DOM-2 methods should not be mixed. However, in this case I cannot use the getElementsBytTagNameNS() since there is no namespace associated with the element. Moreover, the use of the setAttributeNS() is consistent with the use of the getLocalName() and getNamespaceURI() in the printNMap() of the test case. So, the test case seems ok to me, and the fact that there are two equal namespace quailified attributes remains. ...On the other hand I might have misinterpreted the recommendation... I wasn't been able to reproduce the case where the getAttributeNS() returns an unexpected result (e.g. not the value set by setAttributeNS()). I think that in my original implementation it just happen and the binary search was always finding the "old" atrribute value first intead of the new one. Thanks, Mike. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
