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=11552>. 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=11552 Iteration tags do not resynchronize scripting variables after doAfterBody() [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED ------- Additional Comments From [EMAIL PROTECTED] 2002-08-27 00:03 ------- Fixed. AT_BEGIN and NESTED scripting vars now get synchronized after IterationTag.doAfterBody() (they used to get synchronized after doAfterBody() only if the tag handler implemented BodyTag, which was in violation of the spec). They continue to be synchronized after doInitBody() only if the tag handler implements BodyTag. David wrote: > In This Case The First Time The Variable Would Be Synchronized Would Be > After Doafterbody(). On The First Iteration Of The Loop This Would Probably > Throw A Nullpointerexception If You Tried To Use Varatbegin Or Varnested > Inside The Body Of The Tag. In that case it would be the page author's responsibility to check the scripting vars for null, knowing that the scripting vars will be set only after the first body evaluation. I don't think it would make any sense to synchronize a scripting var at the start of the loop, since the scoped variable to synchronize with may not even exist at that point of the tag execution (it may only get defined by IteratorTag.doAfterBody()). -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
