Mailing-List: contact dev-help@myfaces.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "MyFaces Development" <dev@myfaces.apache.org>
Message-ID: <1726271175.1247696474825.JavaMail.jira@brutus>
Date: Wed, 15 Jul 2009 15:21:14 -0700 (PDT)
From: "Andrew Robinson (JIRA)" <dev@myfaces.apache.org>
To: dev@myfaces.apache.org
Subject: [jira] Updated: (TRINIDAD-1483) FocusEvent should contain
 information about the new focus row key
In-Reply-To: <158002294.1242923025666.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Andrew Robinson updated TRINIDAD-1483:
--------------------------------------

       Resolution: Fixed
    Fix Version/s:  1.2.12-core
           Status: Resolved  (was: Patch Available)

> FocusEvent should contain information about the new focus row key
> -----------------------------------------------------------------
>
>                 Key: TRINIDAD-1483
>                 URL: https://issues.apache.org/jira/browse/TRINIDAD-1483
>             Project: MyFaces Trinidad
>          Issue Type: Improvement
>          Components: Components
>            Reporter: Nicolas Pombourcq
>             Fix For:  1.2.12-core
>
>         Attachments: focusevent1.2.11.3.patch
>
>
> When the tree or tree table fires a FocusEvent, a backing bean that wants to keep current on the state of the focus row key needs to call component.getRowKey() to get the new focus row key, which is not very intuitive. getFocusRowKey does not work because if the attribute is bound to an EL expression and the new focus row key is null, it will actually end up resolving the EL expression which would contain the old value.
> The best way to solve this would be to provide the following information on FocusEvent:
> + Object getNewFocusRowKey(): returns the focus row key after the event has been processed;
> + Object getOldFocusRowKey(): returns the focus row key before the event was fired.

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