On Tue, Nov 3, 2009 at 4:02 AM, Martin Marinschek <mmarinschek@apache.org> wrote:
Hi Dan,

> Of course, you have the PreRenderViewEvent, which gets called just before
> the rendering begins, so you have a populated tree at that point. However,
> any changes to the tree are not recorded by the state saving mechanism (I'd
> need to verify that).

this is not true (AFAIK).

Oh, good! I dug into the code a bit more and realized I had things mixed up in my head. Of course state savingn occurs after the encoding.

So perhaps the PreRenderViewEvent is really the hook that satisfies the original use case.

-Dan

--
Dan Allen
Senior Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597

http://mojavelinux.com
http://mojavelinux.com/seaminaction
http://www.google.com/profiles/dan.j.allen