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=15841>. 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=15841 xsp:attribute handled incorrectly ------- Additional Comments From [EMAIL PROTECTED] 2003-01-07 17:10 ------- Before going forward with your proposed fix please make sure that it covers situations like: <xsp:page> <my_root_tag> <xsp:attribute name="foo">bar</xsp:attribute> <xsp:logic> this.contentHandler.startElement("", "test", "test", xspAttr); this.contentHandler.endElement("", "test", "test", xspAttr); </xsp:logic> <tag/> </my_root_tag> </xsp:page> Or even simplier: <xsp:page> <my_root_tag> <xsp:attribute name="foo">bar</xsp:attribute> Some text <tag/> </my_root_tag> </xsp:page> (note that buffering of all the events is not the solution as this might be problem for XSPs generating large XML) To prevent out-of-order execution of xsp:logic... I would recommend enforcing that xsp:attribute or xsp:logic[xsp:attribute] elements go right after opening tag, without other nodes in between (except whitespace). --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
