On Tue, Jun 2, 2009 at 3:07 AM, Ken Paulsen <Ken.Paulsen(a)sun.com&gt; wrote: Navigation. It is all about declarative navigation. After each expression evaluated, the navigation handler is consulted and if a navigation case is matched, the remaining actions are short-circuited. If the navigation is a redirect, the response is wrapped up and the redirect followed (FacesContext#responseComplete()). If their is just a view ID change, the process vamps. The developer does not have to do anything special to get that functionality. Executing a view action (or preRenderViewEvent listener) on a non-faces request is like executing the the restore view. Andy and I worked hard to specify that processing of the f:metadata facet does not build the component tree. That's because the very presence of a view action could circumvent rendering of that component tree, hence making it a wasted operation. The component tree is only built once the preRenderViewEvent listeners complete and the response is not ended. -Dan -- Dan Allen Senior Software Engineer, Red Hat | Author of Seam in Action http://mojavelinux.com http://mojavelinux.com/seaminaction http://in.relation.to/Bloggers/Dan NOTE: While I make a strong effort to keep up with my email on a daily basis, personal or other work matters can sometimes keep me away from my email. If you contact me, but don't hear back for more than a week, it is very likely that I am excessively backlogged or the message was caught in the spam filters. Please don't hesitate to resend a message if you feel that it did not reach my attention.