Slashdot Mirror
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".
There are still things the programmer has to do to ensure that works, but as long as cross-platform rules are followed and environmental configuration is handled sanely, that's been possible since the beginning. It's not often Java's fault that an application won't work on multiple platforms.
Slashdot - where whining about luck is the new way to make the world you want.
Java on Vista: Yes, it Works.
Don't base your assumpsions on half-year old articles on beta software.
We have Smalltalk-based financial systems that process 500000 or more transactions each hour
It can't be that large a European financial institution then. I have clients who specify 20000 transactions per second for their J2EE based trading platforms.
Yes you are right, Java is not popular at all. In fact I am always amazed at the way there are more adverts for Java jobs than just about any other skill (usually number 1 sometimes number 2) when hardly anyone uses it. I guess the companies just like paying for adverts for the fun of it.
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.
1. Why in the world should a FileInputStream/FileReader not automatically use a BufferedInputStream/BufferredReader underneath?
Why do you assume that filereaders must be buffered? I agree that the syntax for reading files is horribly redundant, but I bet with a few static imports, I could make java file handling code look downright pythonish. Write convenience methods for godsakes, don't listen to the aescetic code monks who insist you use nothing but the standard library.
I stopped J2EE at JDK 1.4 and EJB 2.0, so perhaps J2EE 5 has some useful features.
I'll say -- EJB3 is much simpler, for one! It's not without its problems, but it actually makes a lot more sense now. I'd agree that a large number of Sun's API's are bloatastically overengineered, but EJB really has gotten its long-needed overhaul. Other than perhaps optionally dispensing with local interfaces altogether and just using the raw class, I really can't see how it can get any easier.
Sun pushed a standard before they had any applications out there that needed this kind of functionality.
This is a wholly unfounded opinion -- there were in fact plenty of apps that needed what EJB was offering, things like reservation systems that needed to coordinate across multiple vendors. Only problem was that it didn't go far enough for the shops that did need it, and that 90% of business apps were simple CRUD apps that didn't need it at all. Java's got the enterprise and embedded angles covered, but it's still not offering a whole lot toward the middle. Not that I think that offering a mediocre platform is the answer, but they could at least have offered better tooling instead of assuming you'd have a massive team of "enterprise architects" putting apps together. But go look at EJB3 -- there's some signs that they're actually catching on.
And I don't even like Java -- the language itself, that is.
Done with slashdot, done with nerds, getting a life.
> Look at the Java EE 5 API for yourself: http://java.sun.com/javaee/5/docs/api/
Then when you're baffled by reading reference docs, go read the tutorial: http://java.sun.com/javaee/5/docs/tutorial/doc/
Done with slashdot, done with nerds, getting a life.
From the article:
"Java SE 6 is the Best Solution for Vista"
[...]
"J2SE 1.5 Will Also Work
Many of the Vista fixes have already been, or will soon be, back-ported to J2SE 1.5. However, don't look for everything to work exactly the same; our primary focus was to make Java SE 6 the main release vehicle for Vista."
[...]
"J2SE 1.4.2 Will Basically Work..."
That means that if you want to have your Java application working smoothly on Vista, you beter have something that support Java1.6. You can still use 1.5 or even 1.4 but it seems clear that should be a temporary solution.
That said, I also think the GP is FUD. In real development world, supporting a brand new OS always come with a certain amount of work ( even when it is just checking that the application is still running )
Using your definition, no language would ever be WORA because of stupid programmers who make invalid assumptions about the operating environment.
GLaDOS for President 2016! "Well here we are again. It's always such a pleasure." -- GLaDOS, 2011