I like the idea of web-flow like yours. It's not as complicated as Spring Webflow which involves a helluava xml. I hope tapestry5 would adopt your idea.
Cheers. On 12/21/07, jeffrey ai <[EMAIL PROTECTED]> wrote: > > Hi All, > > As you may know or not, T5 doesn't have a web flow framework like the Spring > one yet. Howard mentioned he may add it in the next release. However, our > project cannot wait for that, therefore I have created a simple one on T5. > Here is the general idea, your comments are **GREATLY APPRECIATED**. > > * A WEBFLOW, which is a normal T5 page, injects and contains PAGEs that > will used in this web flow. > > * A PAGE can be used in multiple web flows. A PAGE doesn't have any > knowledge of where to go for next page, previous page or cancel link. All > these knowledge are dynamically populated from a WEBFLOW. > > * A WEBFLOW has some data objects, which are annotated as @ApplicationState. > PAGEs can pick up whatever data they are interested, display them or > populate them. > > * A typical request flow is like below: > => An action request is post back to a PAGE > => A PAGE will do some validation and populate the data > => In onSuccess() method in PAGE, it returns the next page link, which is > populated by WEBFLOW and pointing to an action in WEBFLOW > => A redirection action request is sent to WEBFLOW > => Some onPage() method in WEBFLOW is triggered. It could review the data , > decide the next page and return it. > => A page render request is sent to the next page -- I'm a coder not a drag-n-dropper Blog: http://joshuajava.wordpress.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
