Re: [jsr-314-open] Amendment to section 2.2.1 Restore View

This has been a problem with Facelets from the start. Facelets has always built and serialized the component tree in one fell swoop. I've run into this problem a number of times when trying to add default behavior to a component tree. 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). Perhaps what we need instead is for the state saving to recheck if the component tree state changed by a PreRenderViewEvent listener. (Of course, I think you could do this yourself in one of these listeners, but not the ideal solution). This brings up an important documentation question. At what point in the lifecycle do we recommend that the application add dynamic elements to the component tree? Some guidance would be helpful. -Dan On Mon, Nov 2, 2009 at 4:52 PM, Ryan Lubke <Ryan.Lubke(a)sun.com&gt; wrote: -- 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