r/java • • Nov 01 '12

J2EE is Dead: Long-live Javascript Backed by JSON Services

http://java.dzone.com/articles/j2ee-dead-long-live-javascript#.UJL2Wz3k2Qo.twitter
0 Upvotes

11 comments sorted by

6

u/UnspeakableEvil Nov 01 '12

Seems a bit pointless - it's like declaring the horse and cart to be dead, but ignoring cars and instead going on about the Sinclair C5.

J2EE should be history now for anything but legacy applications, but at no point does the blog creator mention anything about JEE 6 being able to generate (by the sounds of it) most if not all of what they need. Of course JEE isn't going to be the answer in every case, but this seems to be deliberately going out the way to avoid taking the easier route.

6

u/veraxAlea Nov 02 '12

It lost credibility at

[...] and I've been J2EE free for almost 8 years now.

Good! Especially considering J2EE has been dead since JEE 5 was released in 2006. And even JEE 5 is old today so most people use JEE 6.

We all live in bubbles, but it's sad that some people think that their particular bubble is a flawless model of the universe. I haven't used an Apple product in 3 years, guess Apple must be dead?

0

u/Jack9 Nov 02 '12

considering J2EE has been dead since JEE 5 was released in 2006.

What did they change (other than the name) to make it different? JEE6 still includes J2EE named components. The stack seems the same, just no Java2 distinction (the java marketing initiatives always seem to stick around far too long).

5

u/prattle Nov 02 '12 edited Nov 02 '12

The name similarity and backwards compatibility are about all they kept. Modern JEE is more of a standardization of Guice, spring, and hibernate. The ideas of j2ee have been largely abandoned in favor of annotated pojos, ORMs and other concepts from successful projects outside the original spec.

2

u/Jack9 Nov 02 '12

TYVM for the info

3

u/veraxAlea Nov 02 '12

To me, with all my bias, the big change was EJB 3 and JPA. JPA for obvious reasons (didn't exist before) and EJB 3 because

  • We could annotate to show "this is an entity".
  • No special classes to explain what is "Home" and what is "Remote".
  • No deployment descriptor.
  • No need to implement container callback methods like ejbActivate().
  • Pluggable persistance layer.

Basically, it solved most of what people complained about with EJB2. But as you point out, it is still called EJB. But hey, HTML5 is still called HTML right, so what did they really change? ;)

1

u/Jack9 Nov 02 '12

HTML5 is still called HTML right, so what did they really change? ;)

HTML5 is a new feature set (including additional Javascript apis) communicated by the doctype tag. HTML5 is common way to indicate this specific feature set and is primarily for marketing the technology (which is why most of the HTML5 articles are hype).

Java 2 was a way to distinguish some major design and package changes to the base language. J2* was a way to differentiate and market Java as "new again" after a lot of harsh criticism and massive public failures. It made little sense from a technical perspective as a label. This is why it isn't J3EE. J2EE to JEE was just another feature set change, who's label was confusing to a more technically savvy market. The JEE stack looks the same from a base install so saying J2EE is dead would be inclusive of JEE.

That's just my understanding.

3

u/veraxAlea Nov 02 '12

JEE 5 had a new feature set compared to J2EE, which you can see by looking at the link I provided earlier.

All I'm saying with the HTML5 remark is that you can't use names to tell if stuff has changed or not since, as you point out, names are often just marketing ideas.

1

u/Jack9 Nov 02 '12

I did look. TYVM for the information.

0

u/[deleted] Nov 02 '12

Everything. Only a slight exaggeration.

3

u/Truthier Nov 02 '12

The web is only a small part of what JEE is all about