Skip to main content

Wake Me Up When September Ends

Posted by editor on September 28, 2005 at 8:00 AM PDT

The pros and cons of hibernation

Your editors are on the West Coast for some meetings, but we're still on East Coast time. Sleep always seems to fall by the wayside on these trips, but there's so much to do out here. If there weren't now a Fry's Electronics in Atlanta, I would probably have brought a second suitcase just to load up stuff from the Palo Alto store.

I went to college just up the Penninsula from here, so this is sort of my old stomping grounds... but for the proliferation of large and largely empty office towers foolishly built at the end of the dot-com era. There's much that I want to see, but trying to squeeze in trips to campus, Fry's, Tower Records, Compadres, Japantown, and the O'Reilly offices 90 miles north in Sebastopol -- to say nothing of the all-day meetings that are the point of this trip -- is going to come at the expense of sleep.

Moving from sleep to hibernation, two views of the object-relational framework appear in Also in Java Today, one arguing for its use, the other against it.
In What Is Hibernate, James Elliott, author of Hibernate: A Developer's Notebook, introduces the ideas behind, and applications of, this exceptionally popular object-relational mapping framework:
"Hibernate doesn't get in your way; nor does it force you to change the way your objects behave. They don't need to implement any magical interfaces in order to be blessed with the ability to persist. All you need to do is create an XML mapping document telling Hibernate the classes you want to be able to store in a database, and how they relate to the tables and columns in that database, and then you can ask it to fetch data as objects, or store objects as data for you. Compared to most of the alternatives, it's almost magical."

Eric Bruno says this approach has drawbacks: "Typically, those not familiar enough with SQL will choose CMP entity beans or frameworks such as TopLink and Hibernate, which generate queries and help to isolate them from the Java code. Regardless of which you choose, the resulting code will still contain Java-based queries." The article Use Stored Procedures for Java Persistence argues against this approach and shows how writing your own stored procedures can lead to faster, more agile code.

Michael Nielsen wrestles with cross-platform (er, ide) challenges in today's Weblogs:
"Once again, cross-platform development is just out of reach... that is, when thost 'platforms' are IDEs, and the development is for plugins. With extra effort it is do-able; but how many will do it, at long as it requires extra effort?

In Customizing Ocean Gradients, Scott Violet shows "how you can customize the gradients drawn in ocean; from the garish to the minimalist, anything is possible."

Andreas Schaefer wonders about the implications of
JBoss entering the Evil Empire, noting that
"JBoss Inc. and Microsoft announced a partnership of some sort", but notes that it's not clear what that means.

In Projects and
the 54th JavaTools Community Newsletter announces the graduation of the Maven plugin. Built atop the tasks project, the plugin helps you deploy a Maven-generated website to, upload distribution files to, and host artifacts in the Maven repository.

The Java Desktop Community points out another Swing Sightings preview: Mpowerplayer is a free mobile game player for your desktop that lets you find, try, and buy games for your mobile phone. Every game in the extensive catalog is playable and easily purchasable.

In today's Forums,
ingridy discusses complaints
Re: Mustang Early Access JRE size and Early Access AutoUpdate:
"Regarding the JRE bundle size, we are aware that the size is getting increased and we are monitoring the size. Minimum JRE bundle size is actually 8.95 MB not 30.7 MB. Now you might think, then why you are downloading 30.7MB jar file. Ok what you are getting is just a raw image of our JRE bundle in the self-extracting JAR file. Keep that in your mind that self-extracting jar installer is not really designed for our JRE bundle. This was our ultimate choice to release our source bundles only and later due to the customer requirements we have released the JRE/FASTDEBUG bundles in the jar format as well."

kellyohair discusses options for simplified native code in
Re: JNI Improvements:
"Sun Studio 8 had released with a Native Connector Tool (NCT) that would read Dwarf2 debug information from a shared C or C++ library (Solaris or Linux) and automatically create the Java layer interfaces into a native library. Google NativeConnector and you should find some documentation on it. I'm not necessarily recommending it, but Sun has indeed attempted to produced such a beast. For various reasons I'm not sure it is still delivered, but the audience was very limited and the "real" JNI programmers seemed to prefer writing their own code. Giving Java access to native code has it's dangers, and getting it right (and who's 'right') isn't easy either. I agree that using JNI is not easy, it never has been."

In today's
News Headlines

Registered users can submit news items for the href=""> News Page using our
news submission
. All submissions go through an editorial review before being
posted to the site. You can also subscribe to the href=""> News RSS

Current and upcoming Java

Registered users can submit event listings for the href=""> Events Page using our href=""> events submission form.
All submissions go through an editorial review before being posted to the

Archives and Subscriptions: This blog is delivered weekdays as
the Java
Today RSS feed
. Also, once this page is no longer featured as the
front page of it will be
archived along with other past issues in the href=""> Archive.

The pros and cons of hibernation