Thanks for you comments! >>in the step 3 if the specific page would to render the next link, what >>is the purpose of the WEBFLOW? The next link in that page is populated by the WEBFLOW, so it's still the WEBFLOW controlling the navigation.
>>isn't the WEBFLOW'S responsibility to take care of the page navigation?? >>well i guess the purpose of having such a concept of WEBFLOW is to >>decouple the Page presentation from the page navigation Exactly! >>so upon the action, say delete from MyCRUD, MyCRUD::onDelete() was first >>invoked , then the return value (business specific, could be an Object >>to be deleted) will be pass to DeleteConfirmationPage, and invoke the >>@EntryPoint confirmationEntry The point is: in some case, the next page needs to by dynamically decided by the WEBFLOW based on the data user inputed so far. Therefore, the next page might not be DeleteConfirmationPage, but some other page. Spring framework webflow supports this by configuring conditions in XML. But I think using Java is much simpler and testable to developers. Cheers, Jeffrey Ai -- View this message in context: http://www.nabble.com/T5%3A-A-web-flow-idea-on-T5-tp14442158p14459461.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
