I know this thread is too old, but I still have this same issue in T5.3.7.
Since @PageDetached is no longer works, here is how I managed to fix this
for my form:
@Inject private Heartbeat heartbeat;
public void onSubmit()
{
if (request.isXHR())
{
//
It still gave me issues when submitting a form with an error then submitting
it valid, then it would bring up the old values and clobber the real values
(after saving I default back to different data in the form).
So I ammended it to
@PageDetached
void clearValidationTracker() {
Hi,
I've had major issues with this because the ValidationTracker also reloads
old field values which in a non-ajax scenario is great, but in an ajax
scenario has caused it to clobber the proper field values. It has caused
many headaches and I think it really should be handled [better] by default
Thiago, I'm not saying to change the behaviour of the flash persistence. What
I mean is to change the way the Form uses this. For example, the Form could
have two properties: one with @Persist(PersistenceConstants.FLASH) and one
without it, and access the correct one through a private method. If t
Changing the current behavior of the flash persistence can lead to many
hard-to-detect backward compatibility problems. I think a good solution
for this specific scenario is to set the message property to null in a
@PageDetached method.
Maybe a better solution is to create other persistence
Today I found the same problem: persist flash doesn't behave well for an Ajax
request, because the error can be shown two times if you refresh the page
(first one with the form ajax response and second one if you refresh the
page). Maybe when processing the request, if it is an Ajax request, the
v
Hi Geoffrey (and others),
Did you ever figure out a workaround for this issue? I have:
...
Enter E-mail Address
And when I record e-mail address problems in the form, the t:errors
never renders (unless I reload the page as you said). At this point,
I'll eith
On Wed, Apr 22, 2009 at 7:04 PM, Joost Schouten (mailing lists) <
joost...@jsportal.com> wrote:
> On Thu, Apr 23, 2009 at 8:38 AM, Geoffrey Wiseman
> wrote:
> > I wasn't sure if Tapestry did any magic under the covers to work with
> > server-side validation and ajax form submits. I did a quick e
On Thu, Apr 23, 2009 at 8:38 AM, Geoffrey Wiseman
wrote:
> I wasn't sure if Tapestry did any magic under the covers to work with
> server-side validation and ajax form submits. I did a quick experiment and
> it doesn't seem to:
>
> - Create a form, give it a zone to do ajax submit.
> - Create
