Java 5.0 Release Candidate Available

Discussions

News: Java 5.0 Release Candidate Available

  1. Java 5.0 Release Candidate Available (28 messages)

    The first release candidate of Java 5.0 has been released. It seems that people are still not sure about the 5.0 naming scheme as half of the items which display versions show 1.5, and half show 5.0.

    Download Java 5.0 RC

    J2SE Naming and Versioning

    New Features

    Threaded Messages (28)

  2. JDK 1.5 RCII[ Go to top ]

    in the changelog stays that this is the 2 beta
    so they only changed the name from JDK 1.5 to Java 5.0
  3. Version number confusion[ Go to top ]

    According to http://java.sun.com/j2se/j2se-namechange.html, they officially keep using 1.5.0 for the version system properties, installation directories, etc? Will J2SE 6.0 consequently use 1.6.0?

    Don't we love two parallel version number schemes...

    Juergen
  4. Version number confusion[ Go to top ]

    According to http://java.sun.com/j2se/j2se-namechange.html, they officially keep using 1.5.0 for the version system properties, installation directories, etc? Will J2SE 6.0 consequently use 1.6.0?Don't we love two parallel version number schemes...Juergen
    It depends what kind of a developer one is. One person could be a Java 5 developer while another could be a Java 1.5 developer. To sound like experts we probably should insist on using 1.5 ("I have been using Java since ...".)

    On the other hand on your resume you could put "Used Java 1,2,3,4,5 ..." ;-)
  5. Version number confusion[ Go to top ]

    Does this mean Sun will be offering certifications in Jave 1.5 and 5 ;-) ?
  6. Version number confusion[ Go to top ]

    Does this mean Sun will be offering certifications in Jave 1.5 and 5 ;-) ?
    Why pay for certs once, when you can pay for it twice.
  7. Version number confusion[ Go to top ]

    Apparently, you're supposed to use both number schemes at once. According to http://java.sun.com/j2se/1.5.0/docs/relnotes/features.html the name is really

    "Version 1.5.0 of the Java 2 Platform Standard Edition 5"

    no less. Kind of hilarious, in a way.

    I can't wait for "version 1.5.1_03 of Java 2 JDK 5.0.1" to hit the streets...
  8. Sun is using Version Lottery[ Go to top ]

    When on the topic of version number confusion, here is a snippet from Christian Gross' bloggerjacks: "From a Java user's perspective, it makes my head spin to think about Java 2 jumping from version 1.4.2 to version 5.0. This shows that marketing within Sun has taken over and that Sun is playing Version Lottery like many other companies. What bothers me about Version Lotteries is that it confuses users, and you do not know how 'new and improved', new and improved really is.

    What also bothers me is that Sun is using Version Lottery to not make their environment seem as 'immature' as other runtimes that have higher numbers than 1.x. However, the flaw in this logic is that Java's competitors simply need to label their products 2006 and Java would be back to square one. Ideally, Sun should have been original about this and called it Java 2 ^ 5, which reads Java version 2 to the power of 5 or version number 32 -- at least then the version number would sound interesting. Imagine the marketing lines, 'Want the power of five? Get Java 2!' Na ja! life goes on I suppose!"

    Read Christian at: http://www.jaxmagazine.com/itr/online_artikel/psecom,id,611,nodeid,147.html
  9. Version number confusion[ Go to top ]

    Will J2SE 6.0 consequently use 1.6.0?
    Sure, see:
    http://java.sun.com/j2se/codenames.html
  10. Solaris 2.7[ Go to top ]

    One would have thought Sun would have learned their lesson after the Solaris 2.7 / 7 confusion. This is stupid.
  11. Very little for client side[ Go to top ]

    It has been said that the general allways fights the last war.
    There is a lot for server side, like concurent and jmx.

    For client side:
    http://java.sun.com/j2se/1.5.0/docs/guide/javaws/enhancements-1.5.0.html

    VERY VERY LITTE on Desktop.
    Read: http://www.dynamicobjects.com/d2r/archives/002859.html

    Sun, Can we have some attention on RiA using java pls.
    .V
  12. Very little for client side[ Go to top ]

    It has been said that the general allways fights the last war.There is a lot for server side, like concurent and jmx.
    Whoops! Didn't realize I couldn't use those in client/desktop apps.
    For client side:http://java.sun.com/j2se/1.5.0/docs/guide/javaws/enhancements-1.5.0.htmlVERY VERY LITTE on Desktop.Read: http://www.dynamicobjects.com/d2r/archives/002859.htmlSun, Can we have some attention on RiA using java pls..V
    Did you read the response from one of the JWS engineers? Maybe your specific itches didn't get scratched, but I'm not sure "VERY VERY LITTE" is a fair characterization:

    http://java.sun.com/j2se/1.5.0/docs/guide/awt/1.5/index.html
    http://java.sun.com/j2se/1.5.0/docs/guide/swing/1.5/index.html
    http://java.sun.com/j2se/1.5.0/docs/guide/2d/new_features.html

    Obviously, those are just for AWT/Swing/2D, but there's all kinds of stuff that goes into the development of client software besides pure UI. Does JDBC 3.0 help client development? How about JAXP 1.3 with XPath?
  13. Very little for client side[ Go to top ]

    Kris,

    No, *JDBC does not belong on the client*, it belongs on the middle tier, and even then in a DAO.
    Server side, very cool for JMX and Cocnurent.

    Swing (and awt) are just minor bug fixes. Yes, I did read the response, I linked it. The major issues are still there.

    So I still say, imo, 1.5 does very, very little for client side and all you did is link the next level of what I linked. It seems that Sun is trying to fight a server battle and puting in minor resources on the desktop. It will be a pitty if 1.5 is released as it is for people doing UI in Java, it gives then very little.

    My personal main itch is JNLP (aka Web Start) issues that I linked. I do not think many majors server applications will be developed in '05 to be operated in '06. I think legacy server applications will continue operating with minor ehnacments.
    However, on the client side we have Longhorn develoeprs coming out with XAML and great UI (3D). So developers that want to stay on Java will have to defend why they are more efective than XAML. What answer should I give them from Sun?

    .V
  14. Very little for client side[ Go to top ]

    Kris,No, *JDBC does not belong on the client*, it belongs on the middle tier, and even then in a DAO.
    Guess they'd better get started on their web-based versions:

    http://www.jinspired.com/
    http://www.irongrid.com/

    There's all kinds of client apps, Vic, not just the kind that you're interested in.
    Server side, very cool for JMX and Cocnurent.
    Again, what's uncool about using that stuff on the client side?
    Swing (and awt) are just minor bug fixes.
    Depending on your perspective, I suppose reimplementing AWT on Solaris and Linux could be considered a minor bug fix. Same thing with the new skinnable look and feel (Synth).
    However, on the client side we have Longhorn develoeprs coming out with XAML and great UI (3D). So developers that want to stay on Java will have to defend why they are more efective than XAML. What answer should I give them from Sun?
    I'll try to refrain from taking the obligatory shot at the ever-deflating Longhorn since some of the features are apparently being back-ported to XP. Regardless, won't that be more of an issue for J2SE 6.0 (or beyond)? J2SE 5.0 ships at the end of the month, how 'bout Longhorn?
  15. Very little for client side[ Go to top ]

    Kris,

    I am glad you are interested in this. I assume the people that engineer their applications want to make their clients thin and will not be using things they should not be using on the client, for example passing db password from the client from the UI, or other things that do not belong on the client/ui tier.

    Are suggesting we should use concurent w/ Swing instead of SwingWorker to get a responsive UI (when talking to the server)? If not that, where would I use concurent on the UI?

    Look how many packages got added to server and core java, as far as new packages. How many are added for Ui or Swing? Yes, that is minor to me.

    I take it the answer is: Wait till J2SE6 for client and UI.

    J2SE5.0 ship in a month, regardless of feedback. All I am saying, JDNC link pointed out issues w/ mutiple version of Java. That should be fixed, so we do not have to tell people, of, if you want Web Start, you need to re-install J2SE5.1.
    VB has no Network Laucher and the back door is wide open if Sun would work with the users.

    .V
  16. J3SE 6.0[ Go to top ]

    I wonder if we'll have a J3SE 6.0 :)
  17. To confuse you more[ Go to top ]

    Oh, yeh.

    I am a java developer, currently using java version 1.4.1 for J2EE and J2SE. I am a certified Java Programmer and Java2 Programmer, Developer and Architector. I recently attend JavaOne conference. I am a expert in Java naming. I know what's the difference between java 1.5 and java 5.0, difference between Java 1.5 or Java codename Tiger. I am beating my head against wall now to dig out what is Java codenamed Mustang.


    Seriously, in my opinion, Java is at its peak and it will go down a hill from now on. At least, those namings tells us Sun is struggling and down, for sure.
  18. Too little self esteem?[ Go to top ]

    Why should you think Java is going down? Isn't Java the modern Cobol? Rest assure, Java will live forever and it's getting better still. Java is biggest and most successful against everything else. The total market share thwart any other language platform. Don't be insecure. Long live AOP, DI, EL, NL. Java can solve problem other platform don't even know exist.
  19. Silly opinion[ Go to top ]

    Oh, yeh. I am a java developer, currently using java version 1.4.1 for J2EE and J2SE. I am a certified Java Programmer and Java2 Programmer, Developer and Architector. I recently attend JavaOne conference. I am a expert in Java naming. I know what's the difference between java 1.5 and java 5.0, difference between Java 1.5 or Java codename Tiger. I am beating my head against wall now to dig out what is Java codenamed Mustang.Seriously, in my opinion, Java is at its peak and it will go down a hill from now on. At least, those namings tells us Sun is struggling and down, for sure.
    Silly opinion , poor English
  20. 5.0?[ Go to top ]

    Give me a break. If I worked at SUN I would sucker punch people in marketing for being so stupid. Pretty soon Sun is going to start putting letters behind their versions. In another year we will be using Java 8a or Java 9z???

    Then java versioning can become as worthless as oracle versioning!

    Marketing Version -> Technical Version
    9i AS r1 -> 1.0.2 (Should have been called 8i AS)
    9i AS r2 -> 9.0.2 (Should have been called 9i AS r1)
    10g AS -> 9.0.4 (Should have been called 9i AS r2)
    *to be f-ed* -> 10.0.5 (Should be called 10g AS)
  21. Concurrency Library[ Go to top ]

    I think most important enhancement is the addition of java.util.concurrent
    library. It is like addition of java.nio in JDK 1.4

    Besides inclusion of Doug Lea's concurrent library, there are JVM level support.
    java.util.concurrent + java.nio makes Java #1 platform to create high-performance, high-concurrency large scale server-side systems that you can even
    not to be able to develop with C++ taking productivity loss and complexity explosion factors of latter.
  22. Java 5.0 Release Candidate Available[ Go to top ]

    Does this mean it is ready for production use ?
  23. Java 5.0 Release Candidate Available[ Go to top ]

    Poll:

    What is your favorite Java 5.0 feature?
  24. Java 5.0 Release Candidate Available[ Go to top ]

    Poll:

    What is your favorite Java 5.0 feature?
    Okay, it's not my personal number one, but I am missing the enum enhancement in the poll. I think it is far more important than some of the other features listed in the poll.

    Regards,
    Jens
  25. Java 5.0 Release Candidate Available[ Go to top ]

    Big deal on naming the new Java. They just changed it to 5.0 from version 1.5. So now minor release number is major one and they did it right and should have done long time back since release of Java 2 - v1.2.

    I believe they have done the right thing. They have not been changing version numbers every time.

    There are many companies that do the same for marketing as well as other reasons. (Microsoft, Oracle, JBuilder instead of XI is now 2005, etc. and blah blah blah).

    Can't imgine, why there is so much uproar on this issue. They changed it before final release.

    Chill people ;)
  26. http://java.sun.com/j2se/naming_versioning_5_0.html
    http://java.sun.com/j2se/j2se-namechange.html
    http://java.sun.com/j2se/versioning_naming.html
    http://java.sun.com/j2se/codenames.html
  27. JDK[ Go to top ]

    I also noticed that we've swapped back to JDK and not SDK naming for the development environment. I suppose that's good news since I've been calling it the JDK no matter what the version.

    Maybe this is just me, but why do Sun still insist on using the J2 prefix for the platform name?. Why not just call it "Java Platform Standard Edition 5.0" or "Java SE 5.0". The J2 prefix still makes me frown. What possible functionality could Sun ever introduce to justify an name upgrade to the "Java 3 Platform Standard Edition X"?
  28. Java 5.0 Release Candidate Available[ Go to top ]

    I visualized a completelly desperate Sun developer, typing like a maniac in order to meet some deadline. What is he doing? Trying to get this version change done. And, some Sunday at 4 am, he writes a brief memo with a few, enlightening words: "This aint gonna happen, bro!"
    So, I guess we'll have to live with this psichotic duality for some time...
    This versioning crap is all around the industry, so play the game or get yourself a space shuttle and head straight to Mars.

    ....or embrace .NET....

    Regards,
    Martin
  29. Java is a mature and stable development platform. Despite its immature and unstable version names.