I now see your point. Agreed.
I find the page flow "machine" easier to manage, only because all page flow
is in one place, but your idea would fly.
----- Forwarded by Christian Hall/Technology/Equifax on 07/10/2002 08:31 AM
-----
"MacLeod,
Kenny" To: "'[EMAIL PROTECTED]'"
<[EMAIL PROTECTED]>
<Kenny.MacLeo cc:
[EMAIL PROTECTED]
[EMAIL PROTECTED]> Subject: RE: [Tapestry-developer] Setting
page component after form submis
sion
07/10/2002
08:25 AM
> 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.
Protect yourself against identity theft with Equifax Credit Watch. Visit
http://www.creditalert.equifax.com.
This message contains information from Equifax Inc. which may be
confidential and privileged. If you are not an intended recipient, please
refrain from any disclosure, copying, distribution or use of this
information and note that such actions are prohibited. If you have
received this transmission in error, please notify by e-mail
[EMAIL PROTECTED]
-------------------------------------------------------
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
