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

We're ready to auto transform your legacy systems to more robust and secure systems.

Intueor Consulting, Inc. Exodus Framework Suite

Exodus Framework Web Layer Product

Intueor's Exodus Framework Web Layer product to automate Struts 1.x based web layer conversion to Java Server Faces 2.3+, CDI, Bean Validation and PrimeFaces 8+

Third Major Release - In Progress
Second Major Release - June' 2021
First Major Release - Feb' 2018

Exodus Framework ORM Layer Product

Intueor's Exodus Framework ORM Layer product to automate Hibernate 3.x based components transformation to Java Persistence Architecture (JPA) 2.2+

Third Major Release - In Progress
Second Major Release -June' 2021
First Major Release -March' 2019

Automated vs Manual Transformation

Advantages of 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.

Successful Transformations

ReEmployUSA - Consortium of Multi State UnEmployment Insurance System

Converted Struts 1.2.7 based system to Jakarata EE8/JEE 8 based system. Struts related software components (JSP, Tiles, Struts action, action forms, struts validations, tiles config) were transformed to JSF 2.3 Facelets, CDI, Bean Validation based components. The automated transformation produced around 2.6 million lines of source code. First transformed system is successfully running in production since April 2018 and was upgraded successfully in June 2021.

Find out more

Exodus Product Leadership

Exodus Framework Product Leader & Software Architect - Vijay Pandey

Vijay Pandey, Director of Technology, Intueor Consulting, Inc. came up with the novel idea of a first of a kind product

Web Layer - Vijay created the technical architecture, framework, design and developed almost 95% of the codebase of this product and successfully led his testing team to create this innovative and novel product.
ORM Laye

Vijay Pandey, Director of Technology, Intueor Consulting, Inc. came up with the novel idea of a first of a kind product

Web Layer - Vijay created the technical architecture, framework, design and developed almost 95% of the codebase of this product and successfully led his testing team to create this innovative and novel product.
ORM Layer - Vijay created the technical architecture, framework, design and developed the full codebase of this product and currently leading his testing team in the final phase of testing.

Show Less

Find out more