On 4/4/06, Geoff Callender <[EMAIL PROTECTED]> wrote: > > Jeff Lubetkin <jefflub <at> zillow.com> writes: > > > > > Done. http://wiki.apache.org/jakarta-tapestry/FormClientPersistence > > > > I did that pretty quickly, so please let me know if you have any > > questions. > > > > jeff > > > > But the question remains - why should PageLink EVER return state? > How could the next page even read it?
It's an obscure but valid use case. You have client-persistent state on page Foo and a link to page Bar. However, the pageValidate() on Bar redirects back to Foo. So clicking the link for page Bar still renders page Foo, and (in all likelyhood) page Foo still needs that client-persistent state. So, we encode page Foo's client state into all links, even the page link to page Bar. We keep until some other page becomes the active page. -- Howard M. Lewis Ship Independent J2EE / Open-Source Java Consultant Creator, Jakarta Tapestry Creator, Jakarta HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
