Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[microprofile-wg] Addressing EE/MP cooperation

We are pulling up this comment we made out of a long conversation on the Jakarta platform dev list for wider visibility.

Red Hat’s view is that Jakarta EE (EE) should focus on maintaining stability and backwards compatibility as the primary usage for us is EE app modernization via microservices and cloud environment enablement. MicroProfile (MP) features are available for microservice deployment modernization which evolves more rapidly. Once a MicroProfile feature is seen to be useful, integration into an EE architecture that has been able to upgrade past the EE 9.1/EE10 incompatibilities should not see further arbitrary incompatibilities due to yet more namespace changes. EE should strive to extend MP specifications where possible to avoid unnecessary impact on users of EE and MP, and simply put, this is a good practice in specification work. The lack of agreement on rules of engagement via the CN4J alliance, along with the discussions around MP JWT leaves us to believe that competition is where the two working groups appear to be heading. Red Hat is strongly opposed to competing specification based working groups, and until the current competitive stances are resolved and clarified, Red Hat will be reducing activity and sponsorship on all matters other than the resolution of this competition/collaboration issue.

The respective steering committees need to take this topic up in earnest next year.

Back to the top