Big drawback of J2SE 5.0
I've recently made a strong push to use Java in a recent project over .NET. In hindsight, using J2SE 5.0 as opposed to 1.4 was a big mistake.
J2SE 5.0 has been released (not beta) for well over a year so I hardly thought I was pushing the bleeding edge.
What's tricky, is that J2SE 5.0 *itself* was great, very nice new features, and extremely stable. What was terrible is that any web development uses J2EE technologies and J2EE 5.0 isn't close to finished.
This is very confusing to anyone but a Java expert.
Why such a huge lag betwee J2SE 5.0 and J2EE 5.0?
Anyway, this is just a rant... Thanks for reading
[650 byte] By [
Jezza2a] at [2007-10-2 0:29:38]
You don't need J2EE 5.0 if you're working with J2SE 5.0.The version numbers are independent.You can run (most of) the current J2EE application servers on J2SE 5.0 without any problem.
There's no relation between JSE and JEE release numbers.JEE releases require a minimum JSE version but the reverse isn't true. You can use JSE 5.0 quite well together with J2EE 1.4 or 1.3.So there is no drawback, only a misconception on your part.
> Why such a huge lag betwee J2SE 5.0 and J2EE 5.0?Well, I'm waiting for Eclipse 5, so I can finally use J2SE 5 and J2EE 5 with it...*sigh*
If you decide to go Java over .NET, then I suspect you are writing some type of business application in a web server environment. Is this right? Basically, you will want to know your target production environment first. Using Websphere or Weblogic? Which version of these products? Okay, now figure out which JDK/JRE it uses because *that* is the version of Java you will want to code to. If your Websphere uses Java 1.4, use 1.4. It's simple. Don't try to fit a square peg in a round hole - it can be done with a large enough hammer and some major damage to the square peg (and the peg won't look the same afterward), but it can be done. Same with Java.
> > Why such a huge lag betwee J2SE 5.0 and J2EE 5.0?
>
> Well, I'm waiting for Eclipse 5, so I can finally use
> J2SE 5 and J2EE 5 with it...
>
> *sigh*
Rene: Are you obligated to use Eclipse? Could you use Netbeans (or another IDE?)
Netbeans rocks! (mostly)... and its free!
> Rene: Are you obligated to use Eclipse? Could you
> use Netbeans (or another IDE?)
Yes, I am. RSA (Eclipse) with my customer, pure Eclipse in the office. (And JB2005 at home.)
A year or two ago they made Eclipse mandatory. I have to say, nobody ever regretted that decision.
And I don't want to touch anything else, Eclipse is fine enough, and I'm used to do my J2EE stuff in JB2005, which I like pretty much, too. A mix of both would be best, though, JB2005 with the Eclipse editor.
> Netbeans rocks! (mostly)... and its free!So is Eclipse.
yes, Java is way behind the times. I'm using JBuilder 2005, but Java is still only at version 5...
I suspected that as I've been trying to do J2EE 1.4/JSF 1.1/J2SE 5.0 development. Regardless of what is incompatible with what, it's been a very rocky road. I guess Eclipse WTP is still definitely a pre-release product. I will give NetBeans a try and hopefully that is a much more stable web development environment.
Thanks for the responses everyone. My posts never get this much response traffic.
You're being sarcastic and I now understand that the two version numbers aren't related. However, without getting into specifics, I have found many confirmed bugs doing J2EE 1.4/J2SE 5.0 development.
> You're being sarcastic and I now understand that the> two version numbers aren't related. However, without> getting into specifics, I have found many confirmed> bugs doing J2EE 1.4/J2SE 5.0 development.So what?
May i advice that you use the JVM your app server fearutes? No point in writing a Java 5 EJB if you run it on Websphere with IBM's 1.4.2.
think of it this way...
If you write an MS Word document using Word 2003 with t's new features..then you try to open it using MS Word 95, what do you think will happen? The older Word 95 does not supports the new Word 2003 features..futhermore, their byte code is probably different..their tags may have changed.
This is similiar to using Java 5 on a J2EE server that use Java 1.4
Note: Java change their byte code, so 1.4 will not recognized your Java application...there is a "-taraget" feature to compile your application to the specified target (1.4, 1.3, etc)..but i wuould stick with two diffent SDk on my machibe to make life easy.
> I've recently made a strong push to use Java in a
> recent project over .NET. In hindsight, using J2SE
> 5.0 as opposed to 1.4 was a big mistake.
I started using Java in 1998 and it was a big mistake. It's only now 7 years later that commitment is slowly, very slowly, starting to pay off.
I've given up on the claim that Java can be faster than compiled code and am now rewriting parts of my application in C++.
