Book Image

Cloud-Native Development and Migration to Jakarta EE

By : Ron Veen, David Vlijmincx
Book Image

Cloud-Native Development and Migration to Jakarta EE

By: Ron Veen, David Vlijmincx

Overview of this book

Cloud-Native Development and Migration to Jakarta EE will help you unlock the secrets of Jakarta EE's evolution as you explore the migration and modernization of your applications. You’ll discover how to make your code compatible with the latest Jakarta EE version and how to leverage its modern features effectively. First, you’ll navigate the realm of cloud-native development as you demystify containers and get introduced to the Eclipse MicroProfile, a powerful tool in your toolkit. Next, you’ll take the bold step of transitioning your applications from local hardware to the limitless possibilities of the cloud. By following the author’s expert guidance to deploy your Jakarta EE applications on Microsoft Azure, you’ll gain hands-on experience in managing cloud resources. In the final leg of your journey, you’ll explore the world of serverless architecture. You’ll learn to design and run services that are truly serverless, harnessing the potential of the event-driven paradigm for scalability and cost-efficiency. By the end of this book, you’ll have mastered Jakarta EE and become a proficient cloud-native developer. Join us on this exciting journey of transformation and innovation as you pave the way for the future of Jakarta EE and cloud-native development.
Table of Contents (18 chapters)
1
Part 1: History of Java EE and Jakarta EE
4
Part 2: Modern Jakarta EE
8
Part 3: Embracing the Cloud
Appendix A: Java EE to Jakarta EE names
Appendix B: As a Service

Migrating dependencies

With the migration from Java EE to the Jakarta EE namespace, we need to update three dependencies that the project uses. In this section, we will look into how to upgrade the Java version of the project, the Payara application server, and the PrimeFaces dependency.

Upgrading the project

To change the Java version Maven uses, we need to make two changes in the pom.xml file. Inside the pom.xml file located in the root of the project directory, you can find the source and target Maven uses for the cargo tracker application.

Currently, the project uses Java version 7, and inside the pom.xml file, you can find the following two lines that confirm this:

<maven.compiler.source>1.7</maven.compiler.source>
<maven.compiler.target>1.7</maven.compiler.target>

We upgraded the cargo tracker application to the latest long-term support (LTS) version of Java currently available, which is 17. To upgrade the project, replace 1.7 with 17 so...