Obtain a reference to the PersistentFaceState in a bean getter/setter rather than the constructor as a getter is more likely to be called specifically on the user's current page.
Obtain a reference to the PersistentFaceState in a bean getter/setter rather than the constructor as a getter is more likely to be called specifically on the user's current page.
persistentFacesState = PersistentFacesState.getInstance();
Description
With concurrentDOMViews set to false, although a render is requested, the current page may not update in some cases. This may be due to the PersistentFacesState being associated with a previously viewed page.
Ted Goddard
added a comment - The best way would be to get Brad's security demo in its original form (the checked-in version might have a workaround in place).
Is there a way to reproduce this reliably?