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=5264>. 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=5264 DOMBuilder startElement(..) ------- Additional Comments From [EMAIL PROTECTED] 2001-12-04 07:00 ------- Hmmm. Interesting question, but I'm a bit worried about it... If order of these actions matters at all, you'd probably also want to issue the appendChild when the first child is added to the Element. I'm also slightly worried about the precident. If we do this someone may turn around and tell us they don't want the Element added until after its attributes _and_children_ are present... and I don't think we really want to go there. It deserves some thinking about, but my instincts are telling me that your problem should be fixed on the DOM end rather than on the DOMBuilder end. A DOM application really should not be sensitive to the order in which the tree is built.
