Newsletter sign-up

View all newsletters

Enterprise Java Newsletter
Stay up to date on the latest tutorials and Java community news posted on JavaWorld

The pros and cons of JDK 1.1

JavaSoft, Java developers describe the key benefits and shortcomings of the long-awaited Java software toolkit -- and discuss the pain of moving from 1.02

By Kieron Murphy, JavaWorld.com, 04/01/97

Sun Microsystems recently released version 1.1 of the Java Developer Kit to a world of application developers thirsting for increased speed, stability, and security in the APIs used to create Java apps. Weighing in at nearly 700 classes, and boasting significant security, structural, and performance enhancements -- as well as JavaBeans support -- the new JDK release enables programmers to now write applets and large-scale applications that conform to the Java core 1.1 API (and its JavaBeans 1.0 APIs). Initial interest in the upgrade has been significant: Within three weeks of the JDK 1.1 release, developers downloaded more than 220,000 copies of the new toolkit. The immediate obstacle to its full acceptance, though, comes from browser hurdles currently being addressed by such heavyweights as Microsoft and Netscape.

"What we're trying to do with 1.1 is raise the bar," said Eric Chu, product manager for the JDK. "We want to make it easy for people to write fuller, larger-scale applications. We are evolving Java to make it mature enough as a platform that people can write everything from Web-based applets to enterprise-wide applications." (For the complete text of JavaWorld's interview with Eric, see the sidebar Raising the bar with 1.1).

"The main things that turn me on about [JDK 1.1] are the JDBC, the security enhancements, and the JAR format," commented Adrian Scott, chief executive officer of Aereal, a VRML and Java development start-up (www.aereal.com). "In the long term, RMI and object serialization are going to move Java development in a very positive way, especially in combination with JDBC for some really wild distributed apps."

Heavyweight features, lightweight bugs

"We've been using the JDK 1.1 for several months," said Arthur van Hoff, chief technology officer for Marimba. "It certainly is a big step forward in performance, memory efficiency, and functionality. Despite some minor glitches, I'm very happy with it so far. Class unloading, for instance, makes Castanet [Marimba's "push" software] a lot more memory efficient."

"We've encountered a number of glitches associated with JDK 1.1," reported Geoff Vona, the KL Group's (www.klg.com) technical product manager for JClass Chart. "The FCS version contained a gratuitous name change, getId to getID, that broke our code and caused considerable embarrassment for us with our beta testers. And the validate() call in Container makes peer calls that cause the background of the peer to be blanked out. But the transition from JDK 1.0.2 to JDK 1.1 was, for the most part, a smooth process. We love the new event model, as it is very similar to the callback mechanism we introduced in our first Java product back in June of last year."

For the record, the new features in the JDK 1.1 include:

• The JavaBeans 1.0 component architecture
• A new AWT event model
• Inner Classes
• Internationalization
• An enhanced I/O package
• The Java Archive (JAR) file format
• Java Database Connectivity (JDBC)
• A Math package
• Object serialization
• Reflection
• Remote method invocation (RMI)
• Improved security (with those long-promised signed applets)

Also included with the JDK 1.1 are networking enhancements and a score of miscellaneous new or improved classes and protocols. Thrown in for good measure, 1.1 also includes a new wrinkle called the Java Native Interface, or JNI (more on this in a moment).

 

XpoLog Center Correlate application logs with server metrics - XpoLog

About Us | Advertise | Contact Us | Terms of Service/Privacy

Copyright, 2006-2008 Network World, Inc. All rights reserved.