You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Leonardo Uribe (JIRA)" <de...@myfaces.apache.org> on 2011/08/19 21:08:27 UTC

[jira] [Resolved] (MYFACES-3289) Allow f:event listener="#{cc.preRenderViewCallback}" work

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

Leonardo Uribe resolved MYFACES-3289.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.1.2
                   2.0.8

> Allow f:event listener="#{cc.preRenderViewCallback}" work
> ---------------------------------------------------------
>
>                 Key: MYFACES-3289
>                 URL: https://issues.apache.org/jira/browse/MYFACES-3289
>             Project: MyFaces Core
>          Issue Type: Bug
>          Components: JSR-314
>            Reporter: Leonardo Uribe
>            Assignee: Leonardo Uribe
>             Fix For: 2.0.8, 2.1.2
>
>
> This is one of the "most wanted" hacks to do. Long time ago I tried it without success, but now I finally founded and alternative. Following the same principle of MYFACES-3287, we can use a "find component expression" to locate the composite component later and setup the environment correctly. As with MYFACES-3287 if the component is inside a datatable, the code on the listener will only execute once, and not per row, which is something expected and the affected properties on the component has the same limitations. 
> The other part of the hack include use a listener to PostAddToViewEvent to subscribe the listener after the tree is built, so we can calculate the "find component expression" correctly.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira