I just remembered why we do this after RESTOREVIEW. Its because many functions and frameworks do not start up until restore view, so there is often a partially created system before. This is intentional and is not a bug, but hopefully we can find a way to satisfy both needs, perhaps with a context parameter setting to alter behavior for those who wish to use Prettyfaces with those other frameworks like Seam 2. I still think we can work around the jsf null view exception by caching the action method result until after RESTOREVIEW has completed.
Do you play Magic?
Get TopDecked MTG, the #1 Magic App, built by players, for players. Free to use, forever.