. Adamsen [mailto:[EMAIL PROTECTED]
Gesendet: Donnerstag, 6. März 2008 13:23
An: Tapestry users
Betreff: Re: AW: AW: T5: Preventing form success
Yeah, that's what I've been wanting to do for a while, but I haven't had the
time for it. Thanks for the pointers.
-Filip
Martin Kersten sk
Betreff: Re: AW: T5: Preventing form success
Hi,
Well, due to the nature of the content being created/edited, it's necessary to
have the preview on the same page as the form. (This is for a content
management system.) I know about the two requests per page behaviour of
Tapestry, but
)
-Ursprüngliche Nachricht-
Von: Filip S. Adamsen [mailto:[EMAIL PROTECTED]
Gesendet: Donnerstag, 6. März 2008 10:10
An: Tapestry users
Betreff: Re: AW: T5: Preventing form success
Hi,
Well, due to the nature of the content being created/edited, it's necessary to
have the preview on the same pa
Hi,
Well, due to the nature of the content being created/edited, it's
necessary to have the preview on the same page as the form. (This is for
a content management system.) I know about the two requests per page
behaviour of Tapestry, but consider that when a validation error occurs,
the user
Hi Fillip,
I would instantly go for a multi stage / multi-page formular.
Sounds that this preview is a real functionality and so should
be reflected by your component.
The lost of the data is caused by the two requests per response
behavior of tapestry. You may go with persist but I guess a
