Skip to main content

Big Mess

Posted by editor on December 8, 2005 at 8:10 AM PST

A look at the huge stack of JavaOne proposals

Think it's hard to write up and submit a JavaOne session proposal? Try reading a few of them.

In fact, imagine reading nearly 1,400 of them.

That's the task facing Annette Vernon and the JavaOne team. In her blog
JavaOne Excitement Is In the Air, she writes about the deadline deluge of propsals:

The Call for Papers opened on November 1, 2005. The deadline was November 30, 2005: one month to write and submit a brief abstract on some technology to be (hopefully) presented at JavaOne. Was it the Thanksgiving holiday that caught so many of you off-guard or was it plain old-fashioned procrastination? 2006 seems like months away (less than 2!)

On Tuesday, November 29 at 2pm, our content website showed 359 papers submitted. In the next 36 hours, nearly 1100(!) technical talks and birds of a feather proposals were submitted. A huge thanks to the Java developer community for your overwhelming support of the 2006 JavaOne Conference Call for Papers.

On the one hand, it shows tremendous interest in the platform to have almost 1,400 talks proposed for the show. On the other hand... imagine reading all of them, keeping them straight, and then picking the small subset that will make for the best conference.

Also in today's Weblogs,
Carla Mott has an

Interview with GlassFish persistence developers:
"Last week I had the opportunity to talk with Tom Ware and Gordon Yorke who are working on the persistence module in project GlassFish. Both Tom and Gordon are from Oracle's Ottawa, Canada office and have extensive knowledge of the TopLink codebase."

A Short Review of Maven 2, Andreas Schaefer writes:
"This is a follow up of my original concerns about Maven 2 after I attended a presentation by Carlos Sanchez at the LA - JUG last night. In this blog I discuss the points that make me stay with Maven 1 so far but I hope that most of these points can be resolved in the future."

In today's Feature Article,
Java Tech: Image Embossing, Jeff Frisen takes a pixel-level look at
creating an "embossing" effect to give the illusion of depth, manipulating intensities to suggest small ridges and valleys. In this installment of "Java Tech," he introduces an algorithm to perform the embossing effect, and shows how easy it is to implement with Swing and Java2D.

In Also in
Java Today
Jakob Nielsen clarifies one of his most controversial stances in Why AJAX Sucks (Most of the Time): "Judging from the email I receive, the most controversial statement I have made in my Alertbox columns so far was to make 'the use of Ajax' one of the mistakes in my list of top ten mistakes in Web design. For new or inexperienced Web designers, I stand by my original recommendation. Ajax: Just Say No. With respect to the use of ajax by highly skilled Web designers, I have changed my opinion somewhat: people who really know what they are doing can sometimes use ajax to good effect, though even experienced designers are advised to use ajax as sparingly as possible."

Eclipse or NetBeans? How about both? Or neither? Peter Coffee's eWeek opinion piece One Tool Won't Cut It argues against the lock-in that comes with expecting one IDE to perform all your programming tasks. "If I said that integrated programming environments are mixed blessings, any developer who started work in the past 15 years might look at me oddly and say, 'Compared to what?' Most developers probably feel that their choice is between one integrated environment or another. The idea of using entirely separate tools -- an editor from one vendor, a debugger from another and compilers from other vendors still -- is foreign to most developers working today." He goes on to say "I'd rather work with incomplete but complementary views than accept the bullet point on a recent Microsoft briefing chart that read, 'One tool, one framework, one programming model.' No, I don't think so."

In Projects and
the taglibrarydoc project has released version 1.3. taglibrarydoc "is a utility for automatically generating javadoc-style documentation for JavaServer Pages (JSP) Technology Tag Libraries. It accepts a set of tag libraries as input, and generates a set of HTML files as output."

Recently announced on the list, a beta version of JXTA Java SE 2.3.6 is now available. You can build the beta from the CVS sources or download binaries. Community members are asked to test their JXTA applications against 2.3.6 in advance of its scheduled release on December 15th

"Beyond Java"'s efficiency claims, and whether they're comparable to Java, are being analyzed in
today's Forums,
In Re: Chapter 7: Ruby on Rails, archangel writes:
"I agree with many of your points, but there is still a difference in the order of magnitude in development - four months to four days. I doubt the rewrite could have been done in Java that quickly. With regards to the sacrificies made in Ruby, like Java, they're acceptable depending on your point of view. The biggy is less static checking of code - this means that the compiler will save you less (but you've written unit tests right?), but you get a more flexible programming model. There are many others (syntax, code blocks, portability etc.). It depends on your point of view."

Replying to requests
Re: add XML support for java.util.ResourceBundle, mokutsu writes: "Mustang has some enhancements to ResourceBundle so that you can define resources in other formats, like XML. Please check out this tech tip."

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.

A look at the huge stack of JavaOne proposals