Liferay DXP and the Move to Jakarta EE

Liferay has always leveraged the industry standard Java Enterprise Edition (EE) technologies to build DXP. This is a significant and necessary evolution that allows Liferay DXP to run on modern application servers (e.g., Tomcat 10.1, JBoss EAP 8). However, it is a breaking change from previous releases. Custom code and certain dependencies will require updates to be compatible with the new standard.

We understand that this industry-wide shift from Java EE to Jakarta EE represents a significant undertaking. Liferay is committed to making this migration as smooth as possible for our customers and users.

To that end, we are providing documentation and tooling to automate many of the required code changes. Our goal is to equip you with the resources and support needed to successfully navigate this important evolution.

Please note that this page will be updated periodically with new information and resources as it becomes available.

Webinar

A live webinar was conducted on July 29, 2025 covering topics like how to prepare, how you may be impacted, and what resources are available to you.

Resources

Official Documentation

• Upgrading to Jakarta - This article provides a technical overview of the migration as well as an introduction to the available tooling.
• Installing Liferay on an Application Server - For system administrators, instructions have been updated for deploying the Liferay DXP .war file to Jakarta EE compatible application servers.

Guides and Troubleshooting

• Liferay DXP Agent Fails to Start on Jakarta (Tomcat 10) Images with javax.annotation Error

Frequently Asked Questions

To help you plan, we've answered key business and technical questions below. We will continue to update our Comprehensive Jakarta 2025 FAQ as you engage with us and as more information becomes available.