11–20 of 30 posts
Forget J2EE, Java itself is dead. It got a bit of a shot-in-the-arm when Google chose it as a language for Android and it's had some activity around the JVM (e.g. Scala and also Twitter's fork of OpenJVM). But it's dead.
Number one.
Your FUD is utterly pathetic. Utterly. This BS needs to stop. You may not like the language, fine. But dead? FFS.
http://www.tiobe.com/index.php/content/paperinfo/tpci/index....
"The TIOBE Programming Community index is an indicator of the popularity of programming languages."
Java is #1.
Android apps are based on Java. It's not going anywhere any time soon.
Yes, it's worth the time. No, it's not dead, AT ALL. http://www.tiobe.com/index.php/content/paperinfo/tpci/index.... "The TIOBE Programming Community index is an indicator of the popularity of programming languages." Java is #1. Android apps are based on Java. It's not going anywhere any time soon.
Forget J2EE, Java itself is dead. It got a bit of a shot-in-the-arm when Google chose it as a language for Android and it's had some activity around the JVM (e.g. Scala and also Twitter's fork of OpenJVM). But it's dead.
In the open source world things have been looking better. When Oracle dropped commercial support for GlassFish so did interest in GlassFish drop. Some of them migrated to WildFly / JBoss AS/EAP. TomEE has been the only new entry in recent years and from the outside it seems they are struggling to deliver a Java EE 7 (which is two years old) compliant server. Geronimo will be closed down soon. Resin is in its on niche.
The other question is how you define Java EE. If you're using JPA in Tomcat, is that Java EE? If you're using Bean Validation in Spring Boot, is that Java EE?
But then again, has there ever been a time when Java EE had a good rep even with Java developers or was it always something they had imposed on them by "enterprise architects"?
I am not sure people are responding to your question because it is not clear. Would you consider a servlet application server and an app that uses it JavaEE even though it is not technically that? Google app engine uses it extensively , Spring framework is built on it.Dropwizard is very popular for building REST servers and Jersey too (and it is part of JavaEE 7) but these can also be used with a JavaSE stack and a f…
I am not sure people are responding to your question because it is not clear. Would you consider a servlet application server and an app that uses it JavaEE even though it is not technically that? Google app engine uses it extensively , Spring framework is built on it.Dropwizard is very popular for building REST servers and Jersey too (and it is part of JavaEE 7) but these can also be used with a JavaSE stack and a f…
I guess the definition of JavaEE itself is ambiguous then. What was introduced to us in school was Wildfly, EJBs (Session Beans), JSF, Hibernate... That kind of stuff.