Like what you see?

Select language for translation!

Advertise with us!

We sell advert places!
Interested?  Contact us!

Your local time is:

  • CEO Alexander Orlovsky:

Today i want to give my impressions of the JakartaOne Online web conference!


First the bad news:

Jakarta 10 would definitely be pretty different to the previous Jakarta and JEE versions, anyone who thinks to upgrade to the newest Jakarta version please watch out there a dangerous route which you will undergo!

The good news, TomEE from Apache will release a full certified TCK open source app server.

Back to the upgrade paths problem, what you have with Jakarta currently pretty serious situation, if you still run JEE 6, 7 or even 8 JEE application servers prepare for breakage of dependencies, because if you rely on EJB spec, then you will experience lots of problems and EJB would be dropped in newer Jakarta version and the javax namespace was changed (due to legal reasons).

Who actually responsible for support and development in Eclipse foundation?

Well, there exist different types of groups, one is a Jakarta Working group: (major members like RedHat, Oracle, Futjitsu, Payara, IBM) and other group: normal Jakarta committers some of them hired by the members of the Jakarta Working group and some of them are free unpaid committers.

Such situation from enterprise point both good and bad.

Bad: because if you as commercial company want to change the Jakarta specification you need to pay big sum of money to Eclipse Foundation and get the seat at Jakarta Working group and then be able to persuaded other members of the group not to vote for changes, then this is difficult and then if you lucky you will be able to control the specs on which your business applications depend, because in other case you will lose the control over future Jakarta iterations and eventually it would get to the point, that you need to refactor your application , because the spec owner and implementers of the spec decided otherwise!

Good: Many very old parts of JEE in Jakarta would be deprecated and the stuff which would stay it would be maintained and optimized to the current Jakarta specs, which eventually would get you the best possible performance running Jakarta application.

Are you worried?

 Don’t be! There exist other solutions, but you need to put some work in your current application and budget it accordingly!

What I would suggest, you better be with micro frameworks: long term support from Vaadin, Micronaut or and Microprofile.

I personally like the Oracle solution in form of Helidon.


Would Eclipse community or major members of the Jakarta working group provide any useful upgrade guides for the “old” JEE applications?
I got straight answer: NO.

Sure it makes sense, that JEE vendors should care about the clients even more then ever, but really what should they recommend? 

Does IBM , Oracle, RedHat, Fujitsu really have solution for such situation, what would look like the typical upgrade paths for clients which still run JEE6/7 or hopefully more 8?

This change was expected, and Eclipse foundation doing the best of it, but Jakarta 10 it’s not a classical JEE which you used to use in the past!

Here by as executive stockholder of Orlovsky Consulting GbR I recommend my clients to put urgent plans about how you move into new Java ecosystem and of course my company will further support all clients which still use Java EE 6/7/8.

We would do our best to help you to maintain and support you current JEE business applications and even help you with complex upgrade work to newer Java EEor Spring or Vaadin versions!

  • Articles View Hits 524391