Migrate From Javax to Jakarta Namespace

To upgrade from brXM version 15 to version 16, update your implementation project to use the jakarta namespace and upgrade related libraries.

brXM 16 adopts the javax to jakarta namespace change. This change requires upgrading to Jakarta Servlet API 6, Spring Boot 3, Spring 6, Apache CXF 4, XML Web Services API 3, XML Binding API 3, RESTful Web Services 3, Annotations API 2, JAXB Runtime 3, and Mail API 2.

Update Dependencies

The root project POM (org.onehippo.cms7:hippo-cms7-project) manages versions for these third-party libraries. Review your project's POM files for any direct references to these or related libraries. Update your dependencies to align with the versions managed by the product wherever possible. Use the provided version management to ensure consistency between your implementation and the product.

Update Java Imports

Update your Java code to replace all javax.* imports with their jakarta.* equivalents as shown in the table below:

Old importNew import
javax.servletjakarta.servlet
javax.xml.bindjakarta.xml.bind
javax.wsjakarta.ws
javax.annotationjakarta.annotation
javax.mailjakarta.mail
javax.activationjakarta.activation
javax.injectjakarta.inject (*)

(*) The jakarta.inject namespace is used by the Essentials plugin framework. Update this import if you have a custom Essentials plugin. For more information, see the Essentials Plugin Back-End documentation.

Share Feedback
Page: /about/upgrade-guides/v15-v16/migrate-from-javax-to-jakarta-namespace
Section: About
Category *