
- Migration Pattern
- Java framework change
migration-pattern
Migration Pattern
Java Framework Change
Legacy Java systems with EOS frameworks face numerous challenges, including security, support and maintenance, access to new developer functionalities, etc. Failures or delays in modernization can lead to system outages, compliance risks, and loss of competitive advantage.
SoftRoad has helped many customers change legacy Java frameworks (Struts to Spring, Java version upgrade, etc.). Using our proprietary AI-assisted conversion technology, supported by structured analysis, validation, and engineering review, we migrate the legacy Java systems to the updated Java systems that fully comply with industry standards. The resulting systems are rigorously tested for superior quality, highly maintainable, and is generative AI-ready for future maintenance and enhancement.
Success Stories
With our unparalleled AI-assisted modernization technology, supported by structured analysis, validation, and engineering review, we help our clients with their Java framework change initiatives, delivering a true open system with high quality and low costs, which sets us apart from the competition.
A number of our clients presented their migration projects as case studies jointly with SoftRoad at major IT events in Japan. Cover pages shown below are from slides for those speaking sessions.
Case studies reference specific modernization projects delivered across different timeframes and regions. Brand names are used for illustrative purposes only and do not imply endorsement or ongoing commercial relationships.
Case study of system infrastructure renewal at Japan Airlines
at Gartner Application Summit
AIX to Linux
WACs to Struts + Spring
Java upgrade
DB2 upgrade
Renewal of the JAVA framework of the core system!
Development revolution by AI
at IT Modernization Summit
Orteus to SDE
Java upgrade
Oracle upgrade
Applying AppModernizer to the parts purchasing area
at Gartner IT Symposium/Xpo
AIX to Linux
WACs to NSF
Java upgrade
DB2 to Oracle
Doda website framework modernization
at Gartner IT Symposium/Xpo
Seasar2 to Spring
Struts1 to Spring
SaStruts to Spring
XenlonFramework to Spring
Java upgrade
Stop the trend of individual optimization and formulate a “Web standard platform”
Sony Life’s style of reform
at iMagazine
WACs to Spring
Struts1 to Spring
ObjectWorks to Spring
Spring upgrade
Java upgrade
the Modernization of Production Statistics Management system
at ABC Association Event
PowerBuilder to Java
Java upgrade
Oracle upgrade
We have successfully completed over 180 Java migration projects.
Currently, we handle an average of more than 20 Java migration projects per year.
Inevitable Java Framework Update
Frameworks with security and other issues
Struts 1 support ended after April 2013.
Seasar2 support ended after November 2016.
WACs V8 support ended after April 2018 …
Support issues
When updating hardware etc., the Java framework must also be updated.
New technology and function utilization issues
Without access to extensive developer functionality, modifying legacy web applications becomes difficult.
For instance, using Spring Boot can greatly simplify configuration and enable rapid application development.
Inconsistent technical standards
Each Java framework requires a significant investment in terms of manpower, money and material.

Security problems
Even if the system operates and evolves solely within an intranet environment, issues such as multiple investments in vulnerability countermeasures, performance risks, and operational management remain.

Potential Problems in Changing Java Frameworks
Since updating Java frameworks is a one-time event, it is usually handled manually or semi-automatically in most cases.
・Due to the complexity of manual fixes, there is a higher risk of vendor lock-in.
・Significant costs are often hidden under specification changes, maintenance, and other factors, making cost control challenging.
Recommended AI-assisted Automated Conversion
With over 20 years of experience, insights from 950+ migration projects, and a team of 600+ professionals who can manage 50+ projects simultaneously, we developed AppModernizer, a revolutionary AI-assisted conversion tool. Backed by structured analysis, validation, and engineering review, it streamlines migration, reducing both time and cost.

AppModernizer converts legacy Java systems to the latest mainstream technologies and also provides the following advantages in the new system.
☛ New Java framework.
☛ New DB, OS, middleware.
☛ Vulnerability reduction, expansion of number of digits for item IDs. etc.
Maintainability of Source Code after Migration
Change the structure of a Java program

Clear separation of system layers and objects reduces maintenance complexity.
Generate easy-to-understand Java code

Compliance with the latest technical standards and improved readability makes maintenance and specification changes easier.
Track the correlation between variables and processes across the entire system

Through comprehensive analysis of the entire system, the quality of the logic components is improved to a level several times higher than that achievable through manual efforts.
Testing for Superior Quality with Fewer Man-Hours

While most migration companies rely solely on customer-provided test data for quality assurance, we use our proprietary AI-assisted migration technology, backed by structured analysis and engineering reviews, to validate all technical points of the legacy system, ensuring quality while significantly reducing testing time and costs.
Implement Specification Changes During Migration
Prolonged system freezes during migration can be avoided using our catch-up solution.
AppModernizer can perform automated conversion. If customer provides the latest RPG source code after each update, we can integrate the changes by quickly converting them into Java code.
Migration cases
Sales and logistics management system (Struts1, Seasar2 to Spring Boot)
- Development process
- Inventory, migration design, source migration − migration test, system test & user acceptance test support, Go-Live support
- Migration information
- Java 6 to Oracle Java 17
JSP to Thymeleaf
Java6 + Struts1.2.9 + Seasar2 + S2Dao + Ajax + jQuery to Thymeleaf 3.0.15 + SpringBoot 2.6.6 + Mybatis 3.5.9 + Ajax + jQuery3.6
Red Hat Enterprise Linux 5 to Oracle Linux 8.5
Oracle Database 10g/11g to Oracle Database 19c
Keeping Windows 10
IE11 (IE5 mode) to No changes
PrintStream FormEditor to SVFX-Designer 10.1, SVF for PDF 10.1 - Current system scale
- Java:834.6KL, JSP:320.0KL, JavaScript:975.2KL
- Development period
- 16 months
Store facilities management system (Struts2 to Spring Boot)
- Development process
- Inventory, migration design, source migration − migration test, system test & user acceptance test support
- Migration information
- Java 1.6 to OpenJDK 17
Struts2 + Spring Framework + iBatis to SpringBoot 2.7.4 + MyBatis3.5.9
AIX7.1 to Red Hat Enterprise Linux Server 9.2
Oracle Database 11g to Oracle Database 19C
Windows7/Windows10 to Windows7/Windows10/Windows11
IE11(IE7 mode) to Edge118, Chrome118
Keeping IE7 - Current system scale
- Java:381.6KL, JSP:119.2KL
- Development period
- 9 months
Recruiting WEB system (SeaSar2, Struts2 to Spring Boot)
- Development process
- Inventory, migration design, source migration − migration test, system test & user acceptance test support
- Migration information
- Java1.8 to Java11(Amazon Corretto 11)
Seasar2, Struts2 to SpringBoot2.3.2 + Mybatis3.5.1
Windows Server 2008 Enterprise to AWS EC2(Windows Server 2022)
Keeping Oracle Database 12.1.0.2.0, Postgres 9.2.10
Keeping Windows 10 + Chrome v74 - Current system scale
- Java:415.3KL, JSP/JavaScript:296.7KL
- Development period
- 10 months
Insurance management system (WACs,Struts1 to Spring MVC)
- Development process
- Inventory, migration design, source migration − migration test, system test & user acceptance test support
- Migration information
- Java 5 to Java 8
WACsV4.3.4, Struts1.1 to SpringMVC 4.3.10
z/OS V1.10 to Red Hat Enterprise Linux Server 7.2(Azure)
DB2 V8 to DB2 V8 for Linux
Keeping Windows 7/8/10
Keeping IE 11 - Current system scale
- Java/JSP:998.1KL
- Development period
- 27 months
Sales system (Struts1 to Spring MVC)
- Development process
- Inventory, migration design, source migration − migration test, system test support, user acceptance test support
- Migration information
- Java 8 to Java 13 (Oracle JDK)
Struts1.1 + Hibernate to Spring MVC 5.2 + Hibernate 5.4
Oracle Database 11.2 to PostgreSQL 11.7
Keeping Windows 10
IE11 to Edge 88, Chrome 8 - Current system scale
- Java: 461.4KL, JSP: 65.0KL
- Development period
- 7 months
Manufacturing system (WACs to SpringMVC)
- Development process
- Inventory, migration design, source migration − migration test, system test support
- Migration information
- Java 1.8 to Red Hat OpenJDK 17
SQLJ 3.72.44 to SQL + Java(Red Hat OpenJDK 17)
WACs 8.4.1 to SpringMVC 5.3.31 + MyBatis 3.5.11
DB2 v11.1.3.3 to Amazon RDS for PostgreSQL
Windows10 to Windows10, Windows11
Edge (IE5) to Edge (the latest version)
IBM-943 to UTF-8 - Current system scale
- Java: 388.7KL, JSP: 29.3KL, Shell: 26.7KL, SQLJ: 134.8KL
- Development period
- 14 months
Asset trading system (Seasar2 to Spring MVC)
- Development process
- Inventory, migration design, source migration − system test, user acceptance test support
- Migration information
- Java 1.6.0_19 to Amazon Corretto 21.0.2.13.1
Seasar2 to Spring FrameWork 6.1.2 + MyBatis 3.5.15
Oracle Database 12c EE to Amazon RDS for PostgreSQL 16
Windows10 to Windows10, Windows11 (verify operation)
Edge (IE mode) to Edge121.0.2277.112 - Current system scale
- Java: 220.5KL, JSP: 29.3KL, JavaScript: 34.4KL, CSS: 16.8KL
- Development period
- 13 months
Management system
- Development process
- Inventory, migration design, source migration − migration test, system test support, user acceptance test support
- Migration information
- Java 7 to AdoptOpenJDK 8
Teeda + Seasar2 + S2Dao to Thymeleaf3.0.11 + Spring Boot2.3.1 + MyBatis 3.5.3
MySQL 5.7 to SQLServer 2019
Windows 8.1 to Windows 10
Keeping IE 11, Chrome, Firefox, Safari, Edge - Current system scale
- Java: 113.3KL, HTML: 48.2KL, JavaScript: 17.6KL, SQL: 13.2KL
- Development period
- 7 months



