On Fri, Jan 28, 2011 at 4:08 PM, MAX STARETS <[email protected]> wrote: > I just submitted a fix, so barring any new issues we do not have to require > that partial state saving be disabled.
Awesome, thanks for fixing this Max! Wanted to mention that I suspect that we may have some more subtle issues lurking. See: http://lists.jboss.org/pipermail/jsr-314-open-mirror/2011-January/000717.html If the JSF implementations end up going with tree visiting for the partial state save/restore traversals, we'll want to take steps to ensure that we: - Avoid row/model iteration (eg. for components like UIData). And... - Avoid unnecessary context setup/teardown. A seemingly simple way to avoid this would be for the JSF implementations to not use tree visits for the partial state save/restore. An open question is whether a simple facets + children walk (which is what MyFaces does today) is sufficient for these cases. If anyone has thoughts on this, would love to hear it - either here or on jsr-314-open! Andy
