> Correct, but what if the listener has three outcomes? The listener still has full control over the request cycle. It could do anything it wanted to.
But in the simple (and most common) cases, the form can have a defined default "next page". With this approach, you can avoid polluting the listener with workflow logic in the majoirity of cases, whilst retaining the flexibility to _allow_ the listener to manipulate the workflow whenever it wishes to. ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Two, two, TWO treats in one. http://thinkgeek.com/sf _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer
