incubator-adffaces-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arjuna Wijeyekoon (JIRA)" <>
Subject [jira] Commented: (ADFFACES-209) stateManagerImpl does not preserve state for UIViewRoot Correctly.
Date Fri, 29 Sep 2006 18:56:22 GMT
    [ ] 
Arjuna Wijeyekoon commented on ADFFACES-209:

Suggested solution by Adam:

1. we should cache the UIViewRoot.
2. On the subsequent request, we should call restoreState on it.  We still avoid calling processRestoreState
on the tree. However, by calling restoreState on the UIViewRoot we should clear out any residual
state (like stale events) from the previous request while still holding on to valid state
for the new request.
3. to implement this, we need to call saveState on the UIViewRoot so that that state can be
cached and used for the subsequent restoreState call.

I will test this out and upload a patch if it works.

> stateManagerImpl does not preserve state for UIViewRoot Correctly.
> ------------------------------------------------------------------
>                 Key: ADFFACES-209
>                 URL:
>             Project: MyFaces ADF-Faces
>          Issue Type: Bug
>            Reporter: Arjuna Wijeyekoon
> Currently, Trinidad's StateManagerImpl recreates the UIViewRoot component on every request.
> This causes the following bugs:
> 1. not all state is copied from the old UIViewRoot to the new UIViewRoot, specifically:
>  unique id counters and faces listeners, etc ...
> 2. If  the class for UIViewRoot component is redefined in faces-config.xml, this will
break after first the first restoreState call.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message