Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [] Thoughts on JakartaEE

Always good to hear real user feedback, whatever it may be - so thanks for your time indeed.

Ryan and a few other folks are trying to inquire about the viability of a broad based survey to try to ascertain just such things at scale and see what actually makes sense to do with Jakarta EE. Hopefully that happens soon one way or the other. If we do not cross about a 1,000+ verified unique inputs on that survey, I think we have some pretty big challenges to overcome for Jakarta EE aside from the technical ones.

One bright spot is the solid attendance for Jakarta One Livestream. If I am not incorrect, we hit about 1200+ live visitors there on the day, not even counting replays. That indicated there is at least some appetite for forward movement in Jakarta EE. Certainly there was some good attendance and live engagement in the forward looking Jakarta EE sessions, none of which had much to do with MicroProfile really. Here are the replays just in case you are curious what the forward looking Jakarta EE material could be:

Reza Rahman
Principal Program Manager
Java on Azure

Please note views expressed here are my own as an individual community member and do not reflect the views of my employer.

On 9/23/2019 12:47 PM, cen wrote:

After reading a ton of mailing list material and blog posts I'd like to share some thoughts on JakartaEE.

I use a lot of JavaEE and MP daily and contribute to one of MP framework implementations.

The javax naming is very unfortunate but won't really be a big problem for us microservice users since we can update one service at a time. Other than refactoring costs I don't see anything problematic, I think application server users will have much more trouble.

MP was the best thing that happened to JavaEE because it allowed us to take the stable and mature modules from JavaEE and combine them with modern approaches that were missing in the spec. Seeing how successful MP has been so far, I wouldn't merge the projects but collaboration between projects to make specs more interop is welcome. Duplicating specs for roughly the same things would be the major fail.

I have mixed feelings about JakartaEE adding a ton of new features to attract new users. While some new features would be welcome, I see the core modules pretty feature complete. I am not sure people would switch massively to JakartaEE for any reason but I do know existing developers will probably stay if platform feels alive which was not the case for the past few years. As an existing user I am more concerned about the state of some important reference implementations with long standing bugs which are an annoyance in day-to-day work. Looking at - Eclipselink for example screams of abandonware although now that all projects are on github contributing is thankfully much easier. I already had some positive experience contributing to upstream RI so that's feels good.

Best regards, cen

_______________________________________________ mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

Reza Rahman
Principal Program Manager
Java on Azure

Please note that views here are my own as an individual community member and do not represent the views of my employer.

Back to the top