Java EE 6 Platform Draft Published

synodinos writes "The public draft of the Java EE 6 Platform specification has been published and will remain open for public review and feedback until the 23rd of Feb, 2009. Perhaps the most notable part of this delayed draft is the Web Profile, which is first profile in the history of the Java EE platform. The draft is available for download and contains both the Java EE 6 Spec and the Web Profile Spec. There is a poll running at java.net regarding what the community thinks about the new spec. Although participation is yet rather small the results tend to show that the released draft did not cause any excitement."

Comments

JEE 6?

[SirLurksAlot]

I'll settle for 5 at this point. My shop is still using 1.4.2; it feels like I should be writing code on stone tablets! I suspect this is the case in any number of Java shops and it just reinforces the idea that Java is going to become the new COBOL. There is so much "legacy" code out there right now, and because of the inconsistencies between versions I can't see it going away any time soon.

Re:JEE 6?

[Dogtanian]

Java 6 has been out for a long time.

This is about Java EE. The spec that application servers implement (EJB, etc). Not the JVM version.

Yeah, well here's an insightful and funny comment on (I assume) J2EE:-

My hatred of Java has nothing to do with speed. The platform has become a giant morass of 'enterprisey' 'solutions' that create more need for more 'solutions'. And all Java 'solutions' must somehow involve XML, because it's standard, and enterprisey.

Look at my face - is it bothered?

[sgodden]

I've been leading the development of Java applications for around 8 years. On that journey, I have used fewer and fewer features of it with each succesive project.

Nowadays, it seems that specs are a kind of summary of what has been learned from the frameworks which were created in the trenches by people that actually needed to deliver.

My latest project, which has been in development for around 1 year, delivers as a plain web application, and uses Hibernate, Google Guice, AspectJ and Echo3.

It's wonderful.

Sun don't have the capability, and I'm not sure that anyone has, to provide a full and relevant specification that will allow code to be developed that will run on any application server from any vendor.

Instead, choose your implementations and go back to good old OO basics to design interfaces behind which to hide those implementation choices. You don't need Sun to do that for you.

Java EE Irrelevant?

[ssfsx17]

The only times when I've had to look up the EE APIs these days are when I need a refresher on the guts of a HTTPServletRequest/Response or a SQL Connection. Otherwise, Struts, Spring, Hibernate, derivatives of the previously mentioned items and the like are the de-facto standards.