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=4344>. 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=4344 transformation with deleting document-element [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Major |Normal Status|RESOLVED |REOPENED Priority|Other |Medium Resolution|FIXED | ------- Additional Comments From [EMAIL PROTECTED] 2001-11-09 11:40 ------- Reconsidering. From what I've been able to find out, attempting to instantiate an Attribute when there isn't an Element -- and one which has no children yet -- to receive it should be considered an error. That's certainly the case for xsl:attribute... less clear for xsl:copy, though Kay's book suggests it should be. There's also a performance concern here. I'm going to move the fix into the ResultTreeHandler.addAttribute() method. I'm _not_ going to add an error message yet -- we'll keep the silent failure behavior for now -- but we need to reconsider this, so I'm going to reopen the bug at lower severity.
