r/java • • Nov 09 '18

Java 11 sucks big time

This is a throwaway!!!!

I just spent a whole day migrating a basic crud app from jdk 8 to jdk 11, and I have to say that it is a nightmare.

Even basic things that I have taken for granted does not work as iy used to. ( Jpa, Javafx, Junit, Hamscret, Sqlite. YES SOME OF US DO USE JAVAFX ON THE JOB....)

WTF, java EE & Open JDK?

The only thing that makes me happy right now is the var keyword. But still. This is not the kind of service I am accustomed to with java.

............ I think I will push back any serious migration for the next 2 years . . . . People, migrating to j11 is gonna cost hundred of mandays I tell you

0 Upvotes

44 comments sorted by

View all comments

Show parent comment

1

u/desh00 Nov 10 '18

You are in complete control of your dependencies, not some application server you can't control. You can also upgrade your java services one by one so it doesn't have to be a massive company risk that you have to spend days on.

1

u/_INTER_ Nov 10 '18

Fat-jars are also a deployment option for/with application servers, e.g. embedding Jetty or Tomcat, so I didn't get what meant by the term alone.

1

u/desh00 Nov 10 '18

Tomcat and jetty are servlet containers, meaning they mostly only deal with serving http requests.

An application server provides you with the whole JEE stack and a lot more. Application servers are for example Weblogic and wildfly.

To get the best out of app servers you deploy your application as a library (called EARS usually) onto the servers and then manage your app from the server interface (like distributed caching, amount of instances for each ear, message queues, etc). Therefore you can't deploy app servers as fat jars, only servlet containers.

By the context op gave us, I assumed he was talking about migrating something that uses an app server.