Maybe I'm up too late fighting with this, but I think these are valid concerns...
Why does ActionLink seem almost pointless? If you have an action that adds or removes action links (exactly what you need to do to build a tree with them) - you always get StaleLinkExceptions, since the action ids never match up. If you switch to DirectLink you run into the problems below. Why does AbstractPage.renderPage() commit the page changes before calling render()? Or maybe the better question is why does commitPageChanges() automatically lock the recorder? It's hard to modify state within a Foreach if the IPageRecorder has been automatically locked! You would need this feature to incrementally save some changes, or even just save changes after the page has rendered but before it's detached (which you can't do now). Why does a component's state get saved *after* pageDetached() has been called on that component? If you attempt to reset state in that method as recommended in the dev guide, your observed changes are *not* observed. I am calling fireObservedChange() in an action listener, triggered by the Direct service. If you aren't supposed to do this, how exactly do you modify state during a Direct? And if you can't do that, you're back to my first question... -Jason ------------------------------------------------------- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer
