I think he meant, that he opens the database transaction in the
validation step.. then some unknown time later, he commits it within
success. that does sound a bit dirty to me.
On 11/16/10 11:03 AM, Howard Lewis Ship wrote:
On Mon, Nov 15, 2010 at 9:22 PM, Kalle Korhonen
<kalle.o.korho...@gmail.com>wrote:
That's exactly the reason why I typically save and catch the errors in
onValidateForm but commit only in onSuccess. Purists claim it's misuse
of the validate event but in practice makes sense.
Who are these purists? That's exactly what the ValidateForm event is for.
It's your chance to verify the form and associated behavior as a unit prior
to the determination of success and failure.
Kalle
On Mon, Nov 15, 2010 at 9:16 PM, Mihaela Pilon<mihaela.pi...@gmail.com>
wrote:
Hi,
I have a problem where my form field inputs are always cleared after
my "success" event handling.
It's all fine when I can check my inputs prior to "success", such as
inside "validateForm" handler, but sometimes there is no error in
form, but is raised by service layer in form of exception, and I want
to catch it and stay on same page with error shown. Unfortunately in
that case form inputs are cleared. It seems that Tapestry assumes that
once the "success" handler is reached that everything will be fine
afterwards, whereas it doesn't have to.
How do you handle these situations folks, I'm sure this isn't something
unusual?
-MP
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
