Migration of a J2EE EJB 2 application JBoss to EJB 3 Wildfly<\/h1><\/div>The goal of the project was to lift an aging Java application architecture to a newer technical level. In detail, it was about the replacement of Entity Beans by the Java Persistence API.<\/p><\/div><\/div>
![\"Planung](\"https:\/\/www.mybits.de\/wp-content\/uploads\/2023\/04\/MicrosoftTeams-image-31-scaled.jpg\" "\\"Close")
<\/span><\/div><\/i><\/span><\/div>100% J2EE<\/h2><\/div><\/div>\nExperience with J2EE, EJB, JPA, JBoss and Wildfly<\/p>\n<\/div><\/div><\/div>
<\/i><\/span><\/div>5 to 12<\/h2><\/div><\/div>\nTime-critical since “End of Life” of the support<\/p>\n<\/div><\/div><\/div>
<\/i><\/span><\/div>100% Uptime<\/h2><\/div><\/div>\nMigration of the running productive software<\/p>\n<\/div><\/div><\/div>
<\/div><\/div><\/i><\/span><\/div>100% J2EE<\/h2><\/div><\/div>\nExperience with J2EE, EJB, JPA, JBoss and Wildfly<\/p>\n<\/div><\/div><\/div>
<\/i><\/span><\/div>5 to 12<\/h2><\/div><\/div>\nTime-critical since “End of Life” of the support<\/p>\n<\/div><\/div><\/div>
<\/i><\/span><\/div>100% Uptime<\/h2><\/div><\/div>\nMigration of the running productive software<\/p>\n<\/div><\/div><\/div>
<\/div><\/div><\/div><\/div><\/div><\/div>Challenge<\/h2>\n<\/div><\/div><\/div>In addition to the incompatibilities of the libraries used, a particular challenge was to maintain the model-driven approach to the creation of the persistence layer that had been pursued over the last 10 years. At the same time, the architecture had to be changed from EJB2 to EJB3.<\/p>\n<\/div>
- <\/i><\/span>\n
Technology break in the transition from EJB 2 to EJB 3<\/p>\n<\/div><\/li>
- <\/i><\/span>Reduce manual migration<\/div><\/li>
- <\/i><\/span>Avoid manual transmission errors<\/div><\/li><\/ul><\/div><\/div>
- <\/i><\/span>big project, many classes and lines of code<\/div><\/li>
- <\/i><\/span>comprehensive data model<\/div><\/li>
- <\/i><\/span>Get developers mentally in tune with EJB 3 (cut off old habits)<\/div><\/li><\/ul><\/div><\/div><\/div><\/div><\/div>
Realization<\/h2>\n<\/div><\/div><\/div>Familiarization with the project using reverse engineering methods. Step-by-step pragmatic conversion of the individual components.<\/p>\n<\/div><\/div><\/div>
- <\/i><\/span>Removing the EJB 2 Persistence Beans<\/div><\/li>
- <\/i><\/span>Manual migration of a use case<\/div><\/li>
- <\/i><\/span>Proof of concept: use case on new technology functional<\/div><\/li>
- <\/i><\/span>Conversion of the generation of EJB’s to POJO classes<\/div><\/li><\/ul><\/div><\/div>
- <\/i><\/span>Removing the EJB 2 Persistence Beans<\/div><\/li>
- <\/i><\/span>Manual migration of a use case<\/div><\/li>
- <\/i><\/span>Proof of concept: use case on new technology functional<\/div><\/li>
- <\/i><\/span>Conversion of the generation of EJB’s to POJO classes<\/div><\/li><\/ul><\/div><\/div>
![\"App](\"https:\/\/www.mybits.de\/wp-content\/uploads\/2020\/05\/App-Entwicklung-Software-Entwicklung-IT-Consulting-scaled.jpg\")
<\/div><\/div><\/div>![\"austin](\"https:\/\/www.mybits.de\/wp-content\/uploads\/2019\/10\/austin-distel-Imc-IoZDMXc-unsplash.jpg\")
<\/div><\/div><\/div>![\"App](\"https:\/\/www.mybits.de\/wp-content\/uploads\/2020\/05\/App-Entwicklung-Web-Entwicklung-Software-Entwicklung-Programmierer-scaled.jpg\")
<\/div><\/div><\/div><\/div>
The goal of the project was to lift an aging Java application architecture to a newer technical level. In detail, it was about the replacement of Entity Beans by the Java Persistence API.<\/p><\/div><\/div>
<\/span><\/div>100% J2EE<\/h2><\/div><\/div>\nExperience with J2EE, EJB, JPA, JBoss and Wildfly<\/p>\n<\/div><\/div><\/div>
<\/i><\/span><\/div>5 to 12<\/h2><\/div><\/div>\nTime-critical since “End of Life” of the support<\/p>\n<\/div><\/div><\/div>
<\/i><\/span><\/div>100% Uptime<\/h2><\/div><\/div>\nMigration of the running productive software<\/p>\n<\/div><\/div><\/div>
<\/div><\/div><\/i><\/span><\/div>100% J2EE<\/h2><\/div><\/div>\nExperience with J2EE, EJB, JPA, JBoss and Wildfly<\/p>\n<\/div><\/div><\/div>
<\/i><\/span><\/div>5 to 12<\/h2><\/div><\/div>\nTime-critical since “End of Life” of the support<\/p>\n<\/div><\/div><\/div>
<\/i><\/span><\/div>100% Uptime<\/h2><\/div><\/div>\nMigration of the running productive software<\/p>\n<\/div><\/div><\/div>
<\/div><\/div><\/div><\/div><\/div><\/div>Challenge<\/h2>\n<\/div><\/div><\/div>In addition to the incompatibilities of the libraries used, a particular challenge was to maintain the model-driven approach to the creation of the persistence layer that had been pursued over the last 10 years. At the same time, the architecture had to be changed from EJB2 to EJB3.<\/p>\n<\/div>
- <\/i><\/span>\n
Technology break in the transition from EJB 2 to EJB 3<\/p>\n<\/div><\/li>
- <\/i><\/span>Reduce manual migration<\/div><\/li>
- <\/i><\/span>Avoid manual transmission errors<\/div><\/li><\/ul><\/div><\/div>
- <\/i><\/span>big project, many classes and lines of code<\/div><\/li>
- <\/i><\/span>comprehensive data model<\/div><\/li>
- <\/i><\/span>Get developers mentally in tune with EJB 3 (cut off old habits)<\/div><\/li><\/ul><\/div><\/div><\/div><\/div><\/div>
Realization<\/h2>\n<\/div><\/div><\/div>Familiarization with the project using reverse engineering methods. Step-by-step pragmatic conversion of the individual components.<\/p>\n<\/div><\/div><\/div>
- <\/i><\/span>Removing the EJB 2 Persistence Beans<\/div><\/li>
- <\/i><\/span>Manual migration of a use case<\/div><\/li>
- <\/i><\/span>Proof of concept: use case on new technology functional<\/div><\/li>
- <\/i><\/span>Conversion of the generation of EJB’s to POJO classes<\/div><\/li><\/ul><\/div><\/div>
- <\/i><\/span>Removing the EJB 2 Persistence Beans<\/div><\/li>
- <\/i><\/span>Manual migration of a use case<\/div><\/li>
- <\/i><\/span>Proof of concept: use case on new technology functional<\/div><\/li>
- <\/i><\/span>Conversion of the generation of EJB’s to POJO classes<\/div><\/li><\/ul><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div>
Experience with J2EE, EJB, JPA, JBoss and Wildfly<\/p>\n<\/div><\/div><\/div>
5 to 12<\/h2><\/div><\/div>\nTime-critical since “End of Life” of the support<\/p>\n<\/div><\/div><\/div>
<\/i><\/span><\/div>100% Uptime<\/h2><\/div><\/div>\nMigration of the running productive software<\/p>\n<\/div><\/div><\/div>
<\/div><\/div><\/i><\/span><\/div>100% J2EE<\/h2><\/div><\/div>\nExperience with J2EE, EJB, JPA, JBoss and Wildfly<\/p>\n<\/div><\/div><\/div>
<\/i><\/span><\/div>5 to 12<\/h2><\/div><\/div>\nTime-critical since “End of Life” of the support<\/p>\n<\/div><\/div><\/div>
<\/i><\/span><\/div>100% Uptime<\/h2><\/div><\/div>\nMigration of the running productive software<\/p>\n<\/div><\/div><\/div>
<\/div><\/div><\/div><\/div><\/div><\/div>Challenge<\/h2>\n<\/div><\/div><\/div>In addition to the incompatibilities of the libraries used, a particular challenge was to maintain the model-driven approach to the creation of the persistence layer that had been pursued over the last 10 years. At the same time, the architecture had to be changed from EJB2 to EJB3.<\/p>\n<\/div>
- <\/i><\/span>\n
Technology break in the transition from EJB 2 to EJB 3<\/p>\n<\/div><\/li>
- <\/i><\/span>Reduce manual migration<\/div><\/li>
- <\/i><\/span>Avoid manual transmission errors<\/div><\/li><\/ul><\/div><\/div>
- <\/i><\/span>big project, many classes and lines of code<\/div><\/li>
- <\/i><\/span>comprehensive data model<\/div><\/li>
- <\/i><\/span>Get developers mentally in tune with EJB 3 (cut off old habits)<\/div><\/li><\/ul><\/div><\/div><\/div><\/div><\/div>
Realization<\/h2>\n<\/div><\/div><\/div>Familiarization with the project using reverse engineering methods. Step-by-step pragmatic conversion of the individual components.<\/p>\n<\/div><\/div><\/div>
- <\/i><\/span>Removing the EJB 2 Persistence Beans<\/div><\/li>
- <\/i><\/span>Manual migration of a use case<\/div><\/li>
- <\/i><\/span>Proof of concept: use case on new technology functional<\/div><\/li>
- <\/i><\/span>Conversion of the generation of EJB’s to POJO classes<\/div><\/li><\/ul><\/div><\/div>
- <\/i><\/span>Removing the EJB 2 Persistence Beans<\/div><\/li>
- <\/i><\/span>Manual migration of a use case<\/div><\/li>
- <\/i><\/span>Proof of concept: use case on new technology functional<\/div><\/li>
- <\/i><\/span>Conversion of the generation of EJB’s to POJO classes<\/div><\/li><\/ul><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div>
Time-critical since “End of Life” of the support<\/p>\n<\/div><\/div><\/div>
100% Uptime<\/h2><\/div><\/div>\nMigration of the running productive software<\/p>\n<\/div><\/div><\/div>
<\/div><\/div><\/i><\/span><\/div>100% J2EE<\/h2><\/div><\/div>\nExperience with J2EE, EJB, JPA, JBoss and Wildfly<\/p>\n<\/div><\/div><\/div>
<\/i><\/span><\/div>5 to 12<\/h2><\/div><\/div>\nTime-critical since “End of Life” of the support<\/p>\n<\/div><\/div><\/div>
<\/i><\/span><\/div>100% Uptime<\/h2><\/div><\/div>\nMigration of the running productive software<\/p>\n<\/div><\/div><\/div>
<\/div><\/div><\/div><\/div><\/div><\/div>Challenge<\/h2>\n<\/div><\/div><\/div>In addition to the incompatibilities of the libraries used, a particular challenge was to maintain the model-driven approach to the creation of the persistence layer that had been pursued over the last 10 years. At the same time, the architecture had to be changed from EJB2 to EJB3.<\/p>\n<\/div>
- <\/i><\/span>\n
Technology break in the transition from EJB 2 to EJB 3<\/p>\n<\/div><\/li>
- <\/i><\/span>Reduce manual migration<\/div><\/li>
- <\/i><\/span>Avoid manual transmission errors<\/div><\/li><\/ul><\/div><\/div>
- <\/i><\/span>big project, many classes and lines of code<\/div><\/li>
- <\/i><\/span>comprehensive data model<\/div><\/li>
- <\/i><\/span>Get developers mentally in tune with EJB 3 (cut off old habits)<\/div><\/li><\/ul><\/div><\/div><\/div><\/div><\/div>
Realization<\/h2>\n<\/div><\/div><\/div>Familiarization with the project using reverse engineering methods. Step-by-step pragmatic conversion of the individual components.<\/p>\n<\/div><\/div><\/div>
- <\/i><\/span>Removing the EJB 2 Persistence Beans<\/div><\/li>
- <\/i><\/span>Manual migration of a use case<\/div><\/li>
- <\/i><\/span>Proof of concept: use case on new technology functional<\/div><\/li>
- <\/i><\/span>Conversion of the generation of EJB’s to POJO classes<\/div><\/li><\/ul><\/div><\/div>
- <\/i><\/span>Removing the EJB 2 Persistence Beans<\/div><\/li>
- <\/i><\/span>Manual migration of a use case<\/div><\/li>
- <\/i><\/span>Proof of concept: use case on new technology functional<\/div><\/li>
- <\/i><\/span>Conversion of the generation of EJB’s to POJO classes<\/div><\/li><\/ul><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div>
Migration of the running productive software<\/p>\n<\/div><\/div><\/div>
100% J2EE<\/h2><\/div><\/div>\nExperience with J2EE, EJB, JPA, JBoss and Wildfly<\/p>\n<\/div><\/div><\/div>
<\/i><\/span><\/div>5 to 12<\/h2><\/div><\/div>\nTime-critical since “End of Life” of the support<\/p>\n<\/div><\/div><\/div>
<\/i><\/span><\/div>100% Uptime<\/h2><\/div><\/div>\nMigration of the running productive software<\/p>\n<\/div><\/div><\/div>
<\/div><\/div><\/div><\/div><\/div><\/div>Challenge<\/h2>\n<\/div><\/div><\/div>In addition to the incompatibilities of the libraries used, a particular challenge was to maintain the model-driven approach to the creation of the persistence layer that had been pursued over the last 10 years. At the same time, the architecture had to be changed from EJB2 to EJB3.<\/p>\n<\/div>
- <\/i><\/span>\n
Technology break in the transition from EJB 2 to EJB 3<\/p>\n<\/div><\/li>
- <\/i><\/span>Reduce manual migration<\/div><\/li>
- <\/i><\/span>Avoid manual transmission errors<\/div><\/li><\/ul><\/div><\/div>
- <\/i><\/span>big project, many classes and lines of code<\/div><\/li>
- <\/i><\/span>comprehensive data model<\/div><\/li>
- <\/i><\/span>Get developers mentally in tune with EJB 3 (cut off old habits)<\/div><\/li><\/ul><\/div><\/div><\/div><\/div><\/div>
Realization<\/h2>\n<\/div><\/div><\/div>Familiarization with the project using reverse engineering methods. Step-by-step pragmatic conversion of the individual components.<\/p>\n<\/div><\/div><\/div>
- <\/i><\/span>Removing the EJB 2 Persistence Beans<\/div><\/li>
- <\/i><\/span>Manual migration of a use case<\/div><\/li>
- <\/i><\/span>Proof of concept: use case on new technology functional<\/div><\/li>
- <\/i><\/span>Conversion of the generation of EJB’s to POJO classes<\/div><\/li><\/ul><\/div><\/div>
- <\/i><\/span>Removing the EJB 2 Persistence Beans<\/div><\/li>
- <\/i><\/span>Manual migration of a use case<\/div><\/li>
- <\/i><\/span>Proof of concept: use case on new technology functional<\/div><\/li>
- <\/i><\/span>Conversion of the generation of EJB’s to POJO classes<\/div><\/li><\/ul><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div>
Experience with J2EE, EJB, JPA, JBoss and Wildfly<\/p>\n<\/div><\/div><\/div>
5 to 12<\/h2><\/div><\/div>\nTime-critical since “End of Life” of the support<\/p>\n<\/div><\/div><\/div>
<\/i><\/span><\/div>100% Uptime<\/h2><\/div><\/div>\nMigration of the running productive software<\/p>\n<\/div><\/div><\/div>
<\/div><\/div><\/div><\/div><\/div><\/div>Challenge<\/h2>\n<\/div><\/div><\/div>In addition to the incompatibilities of the libraries used, a particular challenge was to maintain the model-driven approach to the creation of the persistence layer that had been pursued over the last 10 years. At the same time, the architecture had to be changed from EJB2 to EJB3.<\/p>\n<\/div>
- <\/i><\/span>\n
Technology break in the transition from EJB 2 to EJB 3<\/p>\n<\/div><\/li>
- <\/i><\/span>Reduce manual migration<\/div><\/li>
- <\/i><\/span>Avoid manual transmission errors<\/div><\/li><\/ul><\/div><\/div>
- <\/i><\/span>big project, many classes and lines of code<\/div><\/li>
- <\/i><\/span>comprehensive data model<\/div><\/li>
- <\/i><\/span>Get developers mentally in tune with EJB 3 (cut off old habits)<\/div><\/li><\/ul><\/div><\/div><\/div><\/div><\/div>
Realization<\/h2>\n<\/div><\/div><\/div>Familiarization with the project using reverse engineering methods. Step-by-step pragmatic conversion of the individual components.<\/p>\n<\/div><\/div><\/div>
- <\/i><\/span>Removing the EJB 2 Persistence Beans<\/div><\/li>
- <\/i><\/span>Manual migration of a use case<\/div><\/li>
- <\/i><\/span>Proof of concept: use case on new technology functional<\/div><\/li>
- <\/i><\/span>Conversion of the generation of EJB’s to POJO classes<\/div><\/li><\/ul><\/div><\/div>
- <\/i><\/span>Removing the EJB 2 Persistence Beans<\/div><\/li>
- <\/i><\/span>Manual migration of a use case<\/div><\/li>
- <\/i><\/span>Proof of concept: use case on new technology functional<\/div><\/li>
- <\/i><\/span>Conversion of the generation of EJB’s to POJO classes<\/div><\/li><\/ul><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div>
Time-critical since “End of Life” of the support<\/p>\n<\/div><\/div><\/div>
100% Uptime<\/h2><\/div><\/div>\nMigration of the running productive software<\/p>\n<\/div><\/div><\/div>
<\/div><\/div><\/div><\/div><\/div><\/div>Challenge<\/h2>\n<\/div><\/div><\/div>In addition to the incompatibilities of the libraries used, a particular challenge was to maintain the model-driven approach to the creation of the persistence layer that had been pursued over the last 10 years. At the same time, the architecture had to be changed from EJB2 to EJB3.<\/p>\n<\/div>
- <\/i><\/span>\n
Technology break in the transition from EJB 2 to EJB 3<\/p>\n<\/div><\/li>
- <\/i><\/span>Reduce manual migration<\/div><\/li>
- <\/i><\/span>Avoid manual transmission errors<\/div><\/li><\/ul><\/div><\/div>
- <\/i><\/span>big project, many classes and lines of code<\/div><\/li>
- <\/i><\/span>comprehensive data model<\/div><\/li>
- <\/i><\/span>Get developers mentally in tune with EJB 3 (cut off old habits)<\/div><\/li><\/ul><\/div><\/div><\/div><\/div><\/div>
Realization<\/h2>\n<\/div><\/div><\/div>Familiarization with the project using reverse engineering methods. Step-by-step pragmatic conversion of the individual components.<\/p>\n<\/div><\/div><\/div>
- <\/i><\/span>Removing the EJB 2 Persistence Beans<\/div><\/li>
- <\/i><\/span>Manual migration of a use case<\/div><\/li>
- <\/i><\/span>Proof of concept: use case on new technology functional<\/div><\/li>
- <\/i><\/span>Conversion of the generation of EJB’s to POJO classes<\/div><\/li><\/ul><\/div><\/div>
- <\/i><\/span>Removing the EJB 2 Persistence Beans<\/div><\/li>
- <\/i><\/span>Manual migration of a use case<\/div><\/li>
- <\/i><\/span>Proof of concept: use case on new technology functional<\/div><\/li>
- <\/i><\/span>Conversion of the generation of EJB’s to POJO classes<\/div><\/li><\/ul><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div>
Migration of the running productive software<\/p>\n<\/div><\/div><\/div>
Challenge<\/h2>\n<\/div><\/div><\/div>In addition to the incompatibilities of the libraries used, a particular challenge was to maintain the model-driven approach to the creation of the persistence layer that had been pursued over the last 10 years. At the same time, the architecture had to be changed from EJB2 to EJB3.<\/p>\n<\/div>
- <\/i><\/span>\n
Technology break in the transition from EJB 2 to EJB 3<\/p>\n<\/div><\/li>
- <\/i><\/span>Reduce manual migration<\/div><\/li>
- <\/i><\/span>Avoid manual transmission errors<\/div><\/li><\/ul><\/div><\/div>
- <\/i><\/span>big project, many classes and lines of code<\/div><\/li>
- <\/i><\/span>comprehensive data model<\/div><\/li>
- <\/i><\/span>Get developers mentally in tune with EJB 3 (cut off old habits)<\/div><\/li><\/ul><\/div><\/div><\/div><\/div><\/div>
Realization<\/h2>\n<\/div><\/div><\/div>Familiarization with the project using reverse engineering methods. Step-by-step pragmatic conversion of the individual components.<\/p>\n<\/div><\/div><\/div>
- <\/i><\/span>Removing the EJB 2 Persistence Beans<\/div><\/li>
- <\/i><\/span>Manual migration of a use case<\/div><\/li>
- <\/i><\/span>Proof of concept: use case on new technology functional<\/div><\/li>
- <\/i><\/span>Conversion of the generation of EJB’s to POJO classes<\/div><\/li><\/ul><\/div><\/div>
- <\/i><\/span>Removing the EJB 2 Persistence Beans<\/div><\/li>
- <\/i><\/span>Manual migration of a use case<\/div><\/li>
- <\/i><\/span>Proof of concept: use case on new technology functional<\/div><\/li>
- <\/i><\/span>Conversion of the generation of EJB’s to POJO classes<\/div><\/li><\/ul><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div>
In addition to the incompatibilities of the libraries used, a particular challenge was to maintain the model-driven approach to the creation of the persistence layer that had been pursued over the last 10 years. At the same time, the architecture had to be changed from EJB2 to EJB3.<\/p>\n<\/div>
- <\/i><\/span>\n
Technology break in the transition from EJB 2 to EJB 3<\/p>\n<\/div><\/li>
- <\/i><\/span>
Reduce manual migration<\/div><\/li>- <\/i><\/span>
Avoid manual transmission errors<\/div><\/li><\/ul><\/div><\/div>- <\/i><\/span>big project, many classes and lines of code<\/div><\/li>
- <\/i><\/span>
comprehensive data model<\/div><\/li>- <\/i><\/span>
Get developers mentally in tune with EJB 3 (cut off old habits)<\/div><\/li><\/ul><\/div><\/div><\/div><\/div><\/div>Realization<\/h2>\n<\/div><\/div><\/div>
Familiarization with the project using reverse engineering methods. Step-by-step pragmatic conversion of the individual components.<\/p>\n<\/div><\/div><\/div>
- <\/i><\/span>Removing the EJB 2 Persistence Beans<\/div><\/li>
- <\/i><\/span>
Manual migration of a use case<\/div><\/li>- <\/i><\/span>
Proof of concept: use case on new technology functional<\/div><\/li>- <\/i><\/span>
Conversion of the generation of EJB’s to POJO classes<\/div><\/li><\/ul><\/div><\/div>- <\/i><\/span>Removing the EJB 2 Persistence Beans<\/div><\/li>
- <\/i><\/span>
Manual migration of a use case<\/div><\/li>- <\/i><\/span>
Proof of concept: use case on new technology functional<\/div><\/li>- <\/i><\/span>
Conversion of the generation of EJB’s to POJO classes<\/div><\/li><\/ul><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div> - <\/i><\/span>
- <\/i><\/span>
- <\/i><\/span>
- <\/i><\/span>