myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Leonardo Uribe (JIRA)" <...@myfaces.apache.org>
Subject [jira] [Resolved] (MYFACES-3965) SKIP_ITERATION visit hint not set when component tree is visited during navigation
Date Fri, 27 Mar 2015 17:50:58 GMT

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

Leonardo Uribe resolved MYFACES-3965.
-------------------------------------
       Resolution: Fixed
    Fix Version/s: 2.2.8
                   2.1.18
         Assignee: Leonardo Uribe

Thanks to Leon Steffens for provide this patch

> SKIP_ITERATION visit hint not set when component tree is visited during navigation
> ----------------------------------------------------------------------------------
>
>                 Key: MYFACES-3965
>                 URL: https://issues.apache.org/jira/browse/MYFACES-3965
>             Project: MyFaces Core
>          Issue Type: Bug
>          Components: General
>    Affects Versions: 2.1.17
>            Reporter: Leon Steffens
>            Assignee: Leonardo Uribe
>             Fix For: 2.1.18, 2.2.8
>
>         Attachments: myfaces-navimpl.diff
>
>
> During navigation, the component tree is visited to publish the PreDestroyView event
to all components in the tree ( org.apache.myfaces.application.NavigationHandlerImpl.handleNavigation).
> When the VisitContext is created, the SKIP_ITERATION VisitHint is not set in the VisitContext.
 The only thing that is set is the SKIP_ITERATION attribute in the FacesContext attribute
map, which is not honoured by libraries such as ICEfaces.
> This can cause an issue if rows in tables are visited and these rows have EL expressions
that access backing beans that, for some or other reason, is no longer available.  In our
case we switch between different contexts in our application before performing the navigation
and the EL expression is evaluated against the new context instead of the old context, causing
issues.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message