Welcome!

Java Authors: Liz McMillan, Walter H. Pinson, III, Maureen O'Gara, Yakov Werde, Tony Bishop

Related Topics: Java

Java: Article

Java's "Tiger" Roars - J2SE Version 1.5.0 Available in Beta Release

Java's "Tiger" Roars - J2SE Version 1.5.0 Available in Beta Release

The next major revision to the Java platform and language, version 1.5.0, is now available.

J2SE 1.5 has been developed under the Java Community Process  as Java Specification Request (JSR) 176, which is led by Sun and an expert group of industry-recognized corporate and individual developers.

The JSR recently won a unanimous vote in the JCP Executive Committee, making way for the beta program to officially open, and accept participants immediately.

New features incorporated since the last "major" release - 1.4.0. - include:

  • New language updates: Metadata, Generics, Enumerated types, Autoboxing of primitive types
  • New JVM Monitoring and Mangement API
  • Improved out-of-box performance
  • New (but compatible) default Java look and feel

"Java technology gives developers the best platform for innovation and ease of development," said Mark Bauhaus, Sun's vice president, Java Web Services, announcing the release.

"J2SE 1.5 marks a tremendous achievement for the Java development community, and is a key milestone in the Java technology roadmap," he continued. "These Java programming language enhancements appeal to a broad variety of Java developers by harnessing the power of the Java platform and allowing developers greater to access it."

Monitoring and manageability is a key focus for the release, Bauhaus pointed out, adding that 1.5 features improvements that allow Java technology-based applications created on the J2SE 1.5 platform to be deployed into existing SNMP-based enterprise management systems.

"This allows the JVM software to be monitored and managed for higher levels of reliability, availability, and serviceability," he explained. 

Also new in J2SE 1.5 platform is the inclusion of the Java Management Extensions (JMX), delivering out-of-the-box deployment to enterprise management systems that support JMX.

For more information on Java 2 Platform, Standard Edition 1.5.0 Beta 1and to participate in the beta program, visit here.

 

More Stories By Java News Desk

JDJ News Desk monitors the world of Java to present IT professionals with updates on technology advances, business trends, new products and standards in the Java and i-technology space.

Comments (8) View Comments

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


Most Recent Comments
Jesse Houwing 02/12/04 05:25:43 AM EST

[quote]There is still something important in my mind that Sun is still missing about the "import" directive, I think it will be very nice if I could write it as following: import java.awt.**; The double star means that it will import every class and every Package [/quote]

this would not work, as the number of classes starting with java* or any other prefix might differ between systems. This will most likely introduce namingconflicts that did not exist on the system of the original developer.

Chris Nelson 02/10/04 09:20:10 AM EST

I add all imports explicitly. Do not use * at all. When using date define the whole class path each instance. These rules enhance maintainability. I agree 100% with Bob Corrick.

Bob Corrick 02/07/04 02:54:21 AM EST

I might start without importing at all, for example:
java.util.Date someUsefulDate; /* This can also be used to refer to a java.sql.Date - which is a subclass of java.util.Date of course. */
When the code repeats itself (eg needs another date reference), it can import just that class or interface, as Tilman suggests. Sometimes the code may end up with repetition of text such as "import java.util." - but it would be explicit, hence easier to maintain. (Easier to identify and delete those unused imports!)
A class that is having ''namespace issues'' (eg must handle both forms of Date) may benefit from refactoring or splitting, to work at one or another level of abstraction.

Tilman Sporkert 02/06/04 07:48:03 PM EST

Regarding the java.util.Date issue... just add a specific
import for that class, i.e.
import java.util.*;
import java.sql.*;
import java.util.Date;
Now you can say
Date myDate;
and it will resolve to java.util.Date;

Francisco 02/06/04 07:27:12 PM EST

Mr. Sibai... pardon my doubt of your sanity, but... are you clinically insane? Have you thought about the logical implications AT ALL?

Consider: import java.util.* and java.sql.* both include a Date class, which requires that the programmer specify java.util.Date instead of Date - every time. That's annoying and suboptimal - and you're asking for EVERY POSSIBLE namespace collision that Java can offer... all in the name of a little bit of convenience so you don't have to bother to, you know, learn Java.

Yuck.

Mohamad M. Jamil Sibai 02/06/04 07:05:24 PM EST

There is still something important in my mind that Sun is still missing about the "import" directive, I think it will be very nice if I could write it as following:
import java.awt.**;
The double star means that it will import every class and every Package located in java.awt, where it is still being written just like the following:
import java.awt.*;
import java.awt.event.*;
not bad for me but it should be exist in the JDK as a powerful programming environment, and consider for the easyness of writing a program:
import java.**;
it is less powerfull I know but its really needed by many programmers.

I Hasan 02/06/04 10:52:37 AM EST

Dan, consider yourself lucky...
we're still stuck on iplanet 4, jdk 1.2.2 !!!

Dan Bernier 02/06/04 07:56:39 AM EST

[sigh] Still stuck on BEA 6.1, JDK 1.3.1...