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=17165>. 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=17165 logic:iterate tag not releasing collections from memory ------- Additional Comments From [EMAIL PROTECTED] 2004-10-15 19:43 ------- Sure, if an app can make use of JSTL, that's great, even preferable. But that won't make this bug go away ;-). Now, if the plan is that by the time Struts moves to JSP 1.2+ it will no longer include this handler, then the discussion is moot. The reason the handler currently has to wait until the release method is invoked to set the reference to null is because the container can determine that it doesn't need to explicitly set a pooled handler's properties (in this case via the handler's setCollection method). If the reference is set to null when the doEndTag method is invoked, then the handler's internal state will be out of sync with what the container expects. I'll have to check into the Standard Taglib stuff... --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]