The Web Flow use case is intended to solve a problem related to the controller logic, which encompasses multi-page navigation (page flow or wizard). If you do not need to have a form divided into several pages (or require several small forms to participate in one transaction), you probably do not need a page flow.
However, most applications need this. Something more than just CRUD can be beneficial.
Pageflows provide a natural data cache and can solve problems that arise when using the back navigation button and multiple frames / tabs.
If you are thinking about how to store data that should live longer than one request (a general but erroneous representation should be stored in HttpSession), you will definitely get something from Web Flow. If you are not doing anything like this and are processing everything in the request area, then the likelihood is that you do not need a web stream.
Update: Web Flow can eliminate the need for specialized controller classes to follow the path to the pages / updates of the form in a predefined workflow. If you don't need to do this, you can save yourself a lot of configuration / complexity just by using MVC.
cwash
source share