Java EE 5 Development Waiting on Vendors
twofish writes "Java EE 5 was a major update and most of the major application server vendors
do not yet have compliant versions released. Dr.
Dobb's reports that this is delaying most solution providers from developing
products based on it, as their customers are not ready for them. However there
is some significant movement among the big players. Among the major vendors,
Sun has released support, WebLogic is close with JBoss following soon after.
Oracle has not announced a road map and IBM is lagging significantly behind,
with full support not due until 2008."
SAP released a Java EE 5 compatible application server a few weeks ago.
This article is about Java EE 5, not the JDK. While it is true that Java EE 5 will require JDK 5, they are not the same thing. J2EE 5 brings significant developer productivity enhancements many stemming from the use of annotations. Alot of this comes from the EJB3 spec, which makes J2EE persistence actually usable vs the old spec (don't take this as a flame, I'm currently waking up from the nightmare that has been my last 3 years of EJB 2 development.) I think that J2EE 5 will be a good step for organizations that can't yet embrace the lightweight develoment model that spring (and others) provides for whatever reason.
As for JDK 5, there are plenty of reasons to use JDK 5, over 1.4, even on a J2EE 1.4 App.
TO name a few...
- Generics, type safety at compilation time
- Enhanced for loops, bye bye, iterator.hasNext()
- Auto Boxing of primitives... bye bye List.insert(new Integer(5)
- Proper enumeration suport.. bye bye scores of static final variables
As for using Java EE 5, there are even more reasons to use it, once ejb 3 specs are stabilized.e.g.
Last but not least, Annotations , bye bye xdoclets, ejb descriptors, . Seriously Annotations, alone, make a very strong case, for adopting Java 5, and Java EE 5.
for the last time people, I am "frodo from middle eaRTH", not "middle eaST".
1.5 added more than just generics, and the bytecode format really is not compatible, so there really isn't much they can do about it.
Use retroweaver to get 1.5 features and annotations in 1.4 code -- http://retroweaver.sourceforge.net/
> There's no reason Java should require 500MB, but that's the size of my Java directory
You have something pretty funny going on there. My jdk1.6 install is 178 megs. I didn't download the separate docs tho, which do add loads and loads of space. Most of the JDK comes with source anyway, and eclipse pulls javadoc right out of source, so I saw little need for it.
Not that 178 megs is small, but I think as long as the full JDK weighs in under 200 megs, it's doing all right.
Now glassfish (the JEE5 reference platform) is monstrous, but it was intended to be the kitchen sink from the start.
Done with slashdot, done with nerds, getting a life.