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=8738>. 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=8738 setPrefix does not allow null parameter [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID | ------- Additional Comments From [EMAIL PROTECTED] 2002-05-27 11:42 ------- Ok, The bug report was not clear. The problem is that, accessing an Element, it is not possible to unset a prefix while it is set to something, nor the setprefix(null) nor setprefix("") work (involved file: org.apache.xerces.dom.ElementNSImpl, method setPrefix, line 201- 231, version: 1.4.4. The handling of a "no-prefix" is not implemented). I only mention the "null" option because a getprefix returns "null" when a prefix is not set (see ElementNSImpl constructor, prefix = null). So, in my opinion, the sequence x.setprefix(x.getprefix()) should always work which, in this case, will generate an error. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
