[jira] [Resolved] (TRINIDAD-2138) partial state saving and client id caching not wroking together

["Gabrielle Crawford (JIRA)" <de...@myfaces.apache.org>]

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

Gabrielle Crawford resolved TRINIDAD-2138.
------------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0.1
         Assignee: Gabrielle Crawford

> partial state saving and client id caching not wroking together
> ---------------------------------------------------------------
>
>                 Key: TRINIDAD-2138
>                 URL: https://issues.apache.org/jira/browse/TRINIDAD-2138
>             Project: MyFaces Trinidad
>          Issue Type: Bug
>            Reporter: Gabrielle Crawford
>            Assignee: Gabrielle Crawford
>             Fix For: 2.0.1
>
>
> In partial state saving when you add a component it calls com.sun.faces.context.StateContext.AddRemoveListener.handleAddEvent(). That method in turn ends up calling getClientId on the added component (in ComponentStruct.absorbComponent). When the view is restored it uses this added client id to look up the saved state in the state map.
> The reason this isn't working is that the added component is returning "outputText2" from getClientId, but the real client id is "pt1:outputText2". The reason this is happening is that UIXComponentBase.setParent is publishing the addToViewEvent before clearing any cached client id.

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