After the use of Spring-WebFlow1.0rc can also feel, my feelings are as follows:
1) First, extract the C in MVC as an independent development module, and focus on various states in webflow. It is reasonable to use the state diagram in the UML diagram for development;
2) Secondly, due to the combination of status charts, I personally feel good. At the same time, I used mock technology during the test, and the framework improved some simple JUnit and easymock extension classes, based on these extension classes, you can easily perform out-of-container tests without the need for Web containers (such as Tomcat) to test these controls;
3) webflow can integrate many features of Spring framework, such as IOC, transaction, AOP, and validator bean. It also provides integration of struts, WW, and spring MVC, however, I personally think that the separation of the web layer is still inferior to the template mechanism of tapestry. I hope there is a new implementation solution for the web layer. In this solution, every HTML element is a component, the most important thing for component development is whether to add new elements, but to add them based on the attributes of the original HTML elements, such as the component method of tapestry, in this way, many requirements can be met in the IDE environment. This is why I do not like to use freemarker. I think it is a failure to provide a custom element method, so I usually hate taglib, however, spring has been supported in this regard, and it also provides some necessary taglib for processing. Fortunately, the above problems are not very practical and barely accepted.
In a few days, I will write an introductory tutorial on SWF. If you are interested, please pay attention to it.
