Java EE Is Moving to the Eclipse Foundation
1–10 of 144 posts
Re: Java EE Is Moving to the Eclipse Foundation
#2Re: Java EE Is Moving to the Eclipse Foundation
#3Java EE going the way of the Dodo
Edit: Sore toes, anyone? Too invested to see clearly? I did enough EE-consulting to have an opinion; it's over-engineered, marketing-driven bullshit; designed to make everything as complicated as possible.
Re: Java EE Is Moving to the Eclipse Foundation
#4Re: Java EE Is Moving to the Eclipse Foundation
#5Re: Java EE Is Moving to the Eclipse Foundation
#6Re: Java EE Is Moving to the Eclipse Foundation
#7Can 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.
[0] http://docs.oracle.com/javaee/6/api/javax/persistence/packag... / http://docs.oracle.com/javase/7/docs/api/javax/sql/package-s...
[1] https://docs.oracle.com/javaee/6/api/javax/servlet/package-s...
[2] http://www.oracle.com/technetwork/java/javaee/jsp/index.html
Re: Java EE Is Moving to the Eclipse Foundation
#8Re: Java EE Is Moving to the Eclipse Foundation
#9Can 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 done by Sun/Oracle.
The problem with JavaEE is, by being too broad and generic, it is incredibly complex and often fails to solve today's developers problems. I mean who cares about JSF(java server face, a way to describe "HTML GUI widgets" in XML) when most applications use a RESTful architecture? Beans session persistance? ... JEE has a lot of technical debt, the word is definitely appropriate here.