I recently struggled with the same issue and in the end implemented a cookie
persist strategy similar to the one on the tapestry wiki. I've since
concluded that cookie persist strategies are far from ideal.
It would be great if tapestry could accommodate non-redirects on form errors
so persistent
So let me be a little clearer:
I don't want to run with SUPPRESS_REDIRECT_FROM_ACTION_REQUESTS =
false, since that affects the entire application. There are definite
benefits to the redirect model with bookmark-able URLs and proper
operation of the browser's back button. However, it seems t
That did fix it, and seems to imply that the client strategy is rather
useless in all but a very few cases. Is there some way to suppress
redirect for a specific action?
Norman Franke
Answering Service for Directors, Inc.
www.myasd.com
On Jul 8, 2009, at 1:30 PM, Robert Zeigler wrote:
I t
I think the previous reply to this post is correct: the form is
correctly submitting w/ the various values stashed as hidden form
fields. But on returning null from onSuccess, to re-render the
current page, tapestry is sending a client redirect to the url for the
page, and that url, of nec
How should the client strategy work? Am I misusing it from the
onSuccess callback?
Norman Franke
Answering Service for Directors, Inc.
www.myasd.com
On Jul 7, 2009, at 7:09 PM, Norman Franke wrote:
On my page, it isn't happening. It gets stuck in the URL. My
"onSuccess()" method does some
Perhaps the form submission leads to an url without parameters:
/yourpage.form.action
but then results in a redirect to /yourpage?t:state=... where the state is
visible?
In T4, if you returned null from a listener it would render the current page.
T5 redirects back to the current page before the
On my page, it isn't happening. It gets stuck in the URL. My
"onSuccess()" method does some further checking, and then returns. I
get a huge URL. Does this not work from onSuccess?
Norman Franke
Answering Service for Directors, Inc.
www.myasd.com
On Jul 7, 2009, at 6:59 PM, Robert Zeigler
I haven't looked closely, but my impression was that T5's
@Persist("client") will encode the values to form fields when there's
a form present. I'm pretty sure that's what's intended...
Robert
On Jul 7, 2009, at 7/75:50 PM , Norman W. Franke wrote:
In the good old T4 days, I was able to pe
In the good old T4 days, I was able to persist form data between
submissions without using any session state since the values were
persisted in the fields themselves. This was very efficient,
particularly for very large forms (with several text areas containing
50K of data each.) As a furth
