Right now I have a system that has a great deal of list forms
from which users select an element and got to a detail form where they do
some stuff and (usually) press submit.
At the end of the submit, I want the user to redirect back to
the list form he was just on.
Right now I'm achieving this with a data structure in my visit
objects that keeps track of the "source" for each edit page the user has
rendered and then redirects back to that particular source when a successful
submit happens. It's sort of a frail solution though as a user could
potentially narf it by bringing up two parallel lists and editing from each
(in which case whichever edit button gets pressed second wins). Likewise
it's a solution that doesn't really use tapestry at all, it harkens back to
my pre-tapestry days when I'd either stash stuff in the session or (more
commonly) use lots, and lots, of hidden fields to allow loopback.
Is there a best practices approach to enabling this sort of
thing within tapestry? Or is my old school approach more or less the way
others have been managing this?
--- Pat
