Onno Scheffers wrote: >> Another idea is displaying a "Your query was submitted"-box in top of >> the form, but after the second submit the effect would be the same: none. > What about using a FLASH-persisted boolean flag that is set to true when > your submit-handler detect a change and updates the database? After submit > is handled, the persisted value makes sure that after the > redirect-after-post your flag is still valid so you can use it to check if a > conditional block needs to be shown. When rendering is done the persisted > value should automatically be removed from the session and therefore reset > to false.
Okay, but when I submit the form a second time, the user will see the same view as before. After both submits the user will see the "Your query was submitted"-box. So after the first submit he will see a change on the page, but not after the second submit. >> Perhaps I could mark the changed values in a different color, but I do >> not know how to access form fields which have been created with a loop >> component. > A custom validation decorator may help here, although you still need a way > during rendering to tell if the field-value has changed. I wrote a blog a > while ago about writing a custom ValidationDecorator: > http://piraya-blog.blogspot.com/2009/06/creating-custom-validationdecorator-for.html. > Maybe it can help you. I will have a look, thank you! - Stephan --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
