You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Andrew Robinson (JIRA)" <de...@myfaces.apache.org> on 2010/10/13 00:30:34 UTC

[jira] Resolved: (TRINIDAD-1919) var and varStatus of the UIXCollection stay around during a visit tree call

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

Andrew Robinson resolved TRINIDAD-1919.
---------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0.0.3-core

> var and varStatus of the UIXCollection stay around during a visit tree call
> ---------------------------------------------------------------------------
>
>                 Key: TRINIDAD-1919
>                 URL: https://issues.apache.org/jira/browse/TRINIDAD-1919
>             Project: MyFaces Trinidad
>          Issue Type: Bug
>          Components: Components
>    Affects Versions: 2.0.0.3-core
>            Reporter: Andrew Robinson
>            Assignee: Andrew Robinson
>             Fix For: 2.0.0.3-core
>
>         Attachments: faces-config.diff, test-case.tar.bz2, TRINIDAD-1919.patch
>
>
> A short-coming of JSF is that there is no provision for resetting the component environment when the context changes during an invokeOnComponent or visitTree call. For example, the collection family components in trinidad inject a var and varStatus variable into the request scope when they are iterating. These variables are left on the request scope if a visit tree or invoke on component call is made while the collection is in scope.
> I propose to make a change to Trinidad to introduce a new API that components may interact with that is basically a stack. The idea is that components that make context sensitive changes would push an object onto a change stack. During an invoke on component call, or a visit tree call, the stack of changes would be suspended. Once the invoke on component or visit tree call is complete, the changes could be resumed.
> This way, in the table example, the var & varStatus could be removed during an IOC/VT call and restored after it is complete.

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