Enterprise Java

Jakarta EE: A Clean Slate

The announcement that Jakarta EE cannot use the javax.* namespace is great news and provides Jakarta EE with a clean slate on which to build and innovate the future of Enterprise Java.

The original proposal

It had been envisioned that the javax.* and jakarta.* namespaces would coexist after Java EE 8 and, as it evolved, the jakarta.* namespace would be used for new features of exiting APIs and the innovation of new APIs. This would have ensured backward compatibility from the start. And overtime the use of jarkata.* would eclipse the old namespace, but never actually replacing javax.* namespace. So, forever more Enterprise Java developers would have to explain why there are two namespaces. A constent reminder of Enterprise Java’s past (something we are trying to move on from).

A new start

Jakarta EE’s hand has been forced and a good thing too. The move by Oracle to disallow the use going forward of the javax.* namespace provides a great opportunity for a fresh start. Enterprise Java can move forward with a clean slate and a new namespace in which to build and innovate in a way that the community has always wanted, unencumbered by the constent reminder of its past in every API.

Migrating forward

The migration route has not been settled and at the time of writing, there are two proposals on the table.

  1. Big band approach – change all namespaces at once
  2. Migrate overtime – change namespaces as required

Both migration approaches will result in the complete migration to the jakarta.* namespace. More details on how this might happen can be found here Transitioning Jakarta EE to the jakarta namespace.

Published on Java Code Geeks with permission by Alex Theedom, partner at our JCG program. See the original article here: Jakarta EE: A Clean Slate

Opinions expressed by Java Code Geeks contributors are their own.

Alex Theedom

Alex Theedom is a Senior Java Developer and has recently played a pivotal role in the architectural design and development of a microservice based, custom built lottery and instant win game platform. Alex has experience of Java web application development in a diverse range of fields including finance, e-learning, lottery and software development. He is the co-author of Professional Java EE Design Patterns and many articles.
Notify of

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Inline Feedbacks
View all comments
Back to top button