DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=31377>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=31377 logic:iterate tag id can destroy attributes of same name [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX ------- Additional Comments From [EMAIL PROTECTED] 2004-09-23 11:14 ------- Richard is right - your two "item" beans are in different scopes and his solution should work. However, the simple (and IMO less confusing) solution is for you to use different attribute names for the bean you're storing in request scope and the "id" you're specifying for the <logic:iterate> tag to use as a page scope bean. You could make an argument that <logic:iterate> should "clean up" its bean once its finished processing, but IMO since there is a perfectly good way of avoiding the type of problem you describe and <logic:iterate> has worked this way a long time I'm reluctant to change it. Niall --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
