No need to persist. The form holds the person's data, and submits it, and since
you are doing Ajax calls there is no redirect - it goes VALIDATE, SUCCESS,
PREPARE_FOR_RENDER, PREPARE all in the same request - so the person data is
still available in onPrepareForRender and goes round trip back ou
On Sat, 05 May 2012 05:28:39 -0300, sommeralex
wrote:
Hi,
Hi!
i have set a browser favicon, and masked forwards of several domains
pointing to my server.
What do you mean by 'masked'?
But not all forwards are showing the favicons. Any ideas why?
Are you sure all maskings are correc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ah, I see - thanks!
Am 06.05.2012 14:37, schrieb Thiago H. de Paula Figueiredo:
> On Sun, 06 May 2012 02:41:13 -0300, Arno Haase
> wrote:
>
>> PS: What's the 'relative assets pitfall'?
>
> Imagine you have a page which URL is /view/edit (the URL i
Updated this post to address comments received to date, best I can.
Still using persistence, though, albeit of the (lower impact/transient)
flash variety:
1. This allows the custom form to both create a new object as well as
submit a partially defined entity for QBE . SUGGESTION: Bean editor
Lance, the 'prepare' event might be fired, but apparently it's not dealt with
by a page component.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Is-it-possible-to-add-Field-validators-at-render-time-tp5682920p5690332.html
Sent from the Tapestry - User mailing list archiv
