Can someone explain what Java EE really means? I tried to parse the bundle and license the last time this came up, and I didn't really get anywhere.
It's basically Java SE + a standarized stack of technologies, that are usually used in server applications: Servlet, EJB, CDI, JSP, JSF, JTA, JPA... Java EE is not the only way of doing serverside java apps - most of systems i've developed used tomcat + spring-* stack, which is not a Java EE platform. I think reading this project page may help clarify what Java EE is: http://openejb.apache.org/apache-tomee.html
Java EE Is Moving to the Eclipse Foundation
31–40 of 144 posts
Re: Java EE Is Moving to the Eclipse Foundation
#32Does this mean that GlassFish will finally have a chance of not sucking?
Re: Java EE Is Moving to the Eclipse Foundation
#33This is IBM finally beating Sun over control of enterprise Java - something they've been fighting for for well over a decade (and much closer to two). IBM has been trying to get the Java process away from Sun - and they even backed an IDE to compete with NetBeans. Eclipse... of the Sun (Microsystems). Apparently, Oracle has finally gotten tired of IBM (through Eclipse) saying "we can do it better" and trying to manag…
I also doubt IBM still cares about Java EE. Their last JSR (Batch/JSR-352) was particularly disgusting and seems to be abandoned already.
Re: Java EE Is Moving to the Eclipse Foundation
#34Re: Java EE Is Moving to the Eclipse Foundation
#35Earlier quoted context omitted.
This is the time when Oracle and IBM both know Java EE is past sell by date. IBM is betting Swift and Go now.
Nothing makes me doubt the future of Swift like this sentence.
https://www.ibm.com/cloud-computing/bluemix/swift
They used to be one of the main contributors of Swift on Linux.
Re: Java EE Is Moving to the Eclipse Foundation
#36Earlier quoted context omitted.
It's basically Java SE + a standarized stack of technologies, that are usually used in server applications: Servlet, EJB, CDI, JSP, JSF, JTA, JPA... Java EE is not the only way of doing serverside java apps - most of systems i've developed used tomcat + spring-* stack, which is not a Java EE platform. I think reading this project page may help clarify what Java EE is: http://openejb.apache.org/apache-tomee.html
Spring + tomcat is built on J2EE, or at least it was 5 years ago when I worked on that stuff. The servlets API is part of J2EE.
Re: Java EE Is Moving to the Eclipse Foundation
#37Can someone explain what Java EE really means? I tried to parse the bundle and license the last time this came up, and I didn't really get anywhere.
> Can someone explain what Java EE really means? I tried to parse the bundle and license the last time this came up, and I didn't really get anywhere. It's no different than Web standards between browsers, it's a collection of API specifications describing how web applications should be architectured in Java. Then different libraries can follow the spec. JavaEE also has a reference implementation which used to be don…
I know of many greenfield projects using it, mainly PrimeFaces.
Re: Java EE Is Moving to the Eclipse Foundation
#38This is IBM finally beating Sun over control of enterprise Java - something they've been fighting for for well over a decade (and much closer to two). IBM has been trying to get the Java process away from Sun - and they even backed an IDE to compete with NetBeans. Eclipse... of the Sun (Microsystems). Apparently, Oracle has finally gotten tired of IBM (through Eclipse) saying "we can do it better" and trying to manag…
This is the time when Oracle and IBM both know Java EE is past sell by date. IBM is betting Swift and Go now.
[0]: https://console.bluemix.net/catalog/?cm_mc_uid=5252549325751...
Re: Java EE Is Moving to the Eclipse Foundation
#39This is IBM finally beating Sun over control of enterprise Java - something they've been fighting for for well over a decade (and much closer to two). IBM has been trying to get the Java process away from Sun - and they even backed an IDE to compete with NetBeans. Eclipse... of the Sun (Microsystems). Apparently, Oracle has finally gotten tired of IBM (through Eclipse) saying "we can do it better" and trying to manag…
Nope, this is Oracle stop caring about Java EE. They are not doing this for Java SE as long as they are caring about Java SE. I also doubt IBM still cares about Java EE. Their last JSR (Batch/JSR-352) was particularly disgusting and seems to be abandoned already.
Good grief. Another mountain of XML programming. It's like the last 10+ years of software engineering never happened.
I wonder how many half completed JSR-352 implementations will emerge.