Struts 1.x+, Hibernate 3+ to JSF 2.2+ & JPA 2.1+ Automated Transformation

This approach involves undertaking the task of conversion in an automated and efficient manner using custom developed software components, libraries, and tools/utilities. The advantages of this approach include: 

• The ability for the current system to continue with the design, development, customization, testing and implementation of any new feature or maintenance fixes, independent of the conversion effort. The conversion approach using automated means could essentially be performed as an independent activity right up to the point of cutover, at which point, the entire codebase (or a portion of it, as is deemed appropriate) can be converted automatically. 
• The time, effort and resources necessary to convert the Web Layer components using automated means are significantly lower than those required for manual conversion. 
• An automated approach offers a mechanism to develop Web Layer Components using the Target Technologies, consistently across the team of developers, i.e., minimizing the effect of personal coding styles and individual standards. 
• An automated approach provides the ability to manage multiple streams/branches of source code along with new set of code artifacts. At any given point of time, a specific Apache Struts-based code branch/stream can be transformed using the conversion programs. With a minimal effort, the automated approach can be enhanced to incorporate software controller code that will allow some portions of the current system to utilize the Apache Struts Framework while other portions use the JSF/PF Framework.  

 Disadvantages of Manual Transformation: This approach involves the manual scanning, identification of each individual line of code and character, and manually writing the new code using the Target Technologies. This approach is not only time consuming and laborious, but also presents a significant risk particularly because of the following reasons: 

• Mostly any source codebase is dynamic with a significant portion of the code being newly written or existing code being customized to accommodate the business needs of business. In this environment, manual conversion creates a challenge in ensuring consistent use of the new Web Application Framework across the Source Codebase. 
• Additionally, during this period, the source codebase is also undergoing regular life cycle activities such as maintenance, periodic releases, and regular defect-fixing in the production environment, which further complicates the manual conversion approach. 
• The manual approach does not provide adequate flexibility for the business to determine a specific point in time for the cutover, i.e., converted code being used in the development and maintenance streams of work, because of the longer time necessary for manual conversion.
• The approach also tends to be cost prohibitive considering the size of the code to be converted, skill sets required and the number of resources required.