S1 with S2 it will overflow. Both structures are complex, so maintenance costs are doubled or more. So the strategy is to switch to S2 completely.
In both environments, the MVC pattern is implemented. Divide the application into three parts that must be transported separately: model, controller, and view. Order is not important, but logically implied to follow MCV order. A model that you probably wonβt change, for the controller part you need to rewrite the configuration, the representation is the hardest part, you need to rewrite the S1 tags to S2 tags.
Migrating Struts 1.x to Struts 2.x:
Struts1 struts1. > , solutions strategy > , . . Struts1 JSP Struts2, Struts1, .
Struts Spring:
- Struts2. , Struts , : Struts Dead? III: Struts (Struts is ) .
InfoQ: