<div class="gmail_quote">On Tue, Nov 3, 2009 at 11:29 AM, Dan Allen <span dir="ltr"><<a href="mailto:dan.j.allen@gmail.com">dan.j.allen@gmailcom</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br><div class="gmail_quote"><div class="im"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><br>
</div><div>> ** Allows the application to modify the state of any component in the tree<br>
> just before the tree state is written out. Does that seem useful?<br>
<br>
</div>I have never had a use-case for a callback after rendering and before<br>
saving the state. Why would that be necessary - a concrete use-case?<br>
If I create components dynamically, I make them transient, so they are<br>
not save-stated anyways - so no need to modify the state of components<br>
before save-stating.<br></blockquote></div><div><br>I'll agree it is an edge case. Originally when I created the secure token tag for Seam, I wanted to add markup to the encoded HTML and put the token in the tree state. I decided instead to do that work during encoding in a component tag. The downside is that I couldn't add the functionality to existing pages without modification.<br>
</div></div></blockquote><div><br>But now with PreRenderViewEvent, I could add the component dynamically and get the same result. So perhaps this isn't necessary after all.<br><br>-Dan<br></div></div><br>-- <br>Dan Allen<br>
Senior Software Engineer, Red Hat | Author of Seam in Action<br>Registered Linux User #231597<br><br><a href="http://mojavelinux.com">http://mojavelinux.com</a><br><a href="http://mojavelinux.com/seaminaction">http://mojavelinux.com/seaminaction</a><br>
<a href="http://www.google.com/profiles/dan.j.allen">http://www.google.com/profiles/dan.j.allen</a><br>