[jira] Resolved: (WW-295) IteratorTag to put itself onto the stack

["Tom Schneider (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/struts/browse/WW-295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Schneider resolved WW-295.
------------------------------

    Resolution: Won't Fix

Unless we get some updated patches, this won't be happening.

> IteratorTag to put itself onto the stack
> ----------------------------------------
>
>                 Key: WW-295
>                 URL: https://issues.apache.org/struts/browse/WW-295
>             Project: Struts 2
>          Issue Type: Improvement
>    Affects Versions: WW 2.0-beta1
>            Reporter: Mike Mosiewicz
>         Assigned To: Patrick Lightbody
>             Fix For: Future
>
>
> I think that IteratorTag should push itself on the stack (and pop it away when it's finished).
> This way you are able for example to built visible components that are iterator-aware. 
> For example you could assume that you have a reusable visual component that may be used inside iterations. In case when iterator is actually accessible somewhere, the component may be able to get current iteration status without knowing any context variables that iterator exported.
> Currently you have to put variable-name contract between components. In case when iterator is on the stack, no such contract is necessary, cause the component is able to answer the question "is there any iterator I'm called from?".
> This also means that iterator status should not be optional. Instead it should rather be lazy-initialized.
> Maybe I'll just commit a patch.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.