Skip to main content

Keep On Working

Posted by editor on April 26, 2007 at 7:33 AM PDT

A big JavaOne crunch, or 50 little crunches?

Those of you with big announcements to drop at JavaOne have it easy, I'm telling you. No, just kidding, of course -- I know people are crunching pretty hard to have their stuff ready for next week's show. But outside of the single-minded developer focus, for a lot of us involved with the show, the weeks leading up to JavaOne have been a series of mini-crunches.

So far, we've been lining up bloggers for our usual front-page blog-centric coverage, setting up a podcasting infrastructure for new content and the Community Corner mini-talks from JavaOne, arranging the Community Leaders weekend, etc. On the O'Reilly plate, I've been working with marketing on the message for the O'Reilly booth, the crossword puzzle for the daily JavaOne Today newspaper, tracking down e-mail addresses of some FOO's who may or may not be at the show, etc. And I should rehearse my BoF presentation. And write my mini-talk. And hack some more functionality into Keaton so there's something non-trivial to show.

See, it's not one big scary project to work on, just lots of little things piling up. So, if you're waiting on something from me, nagging me about it in my current mood would be a really bad idea.

Having mentioned the new podcast infrastructure, I don't want to spoil anything, but you'll be seeing more podcast content in the near future. As with last year, we'll be podcasting all the mini-talks from the booth's "Community Corner". However, this year, instead of trying to blast everything out in near real-time (an idea predicated on the idea of trying to capture the excitement of the show), we're going to dole them out over the course of several weeks, maybe even months. This approach should be a lot more feed-friendly: instead of mini-talks getting blown away on your computer by new ones after just a few hours, you'll have time to find the talks that interest you.

There are going to be other feeds too, and a "super feed" of all content... but let's not get ahead of ourselves. Let's take a moment to highlight a new podcast feed that's up and running, the Mobile & Embedded Podcast. This series, produced by former Editor Daniel Steinberg, will focus on the people and projects in the small device space. With a podcatcher like Juice or iTunes, you can subscribe to the podcast feed, and iTunes users can also find the podcast in the iTunes store. We're spotlighting the first episode as our Feature Article today.
Mobile and Embedded Podcast 1: Introduction to the Community
Community Leader Roger Brinkley and Technical Evangelist Terrence Barr describe the resources available for Mobile and Embedded developers.

Speaking of ME development, in today's Weblogs, Mauricio Leal answers the rhetorical question Ok, I've developed my Java ME application. Now what?
"You spend hours developing a very cool JavaME application and then, you manage to install into your device and you start play with it. Is that all ? Is your JavaME application ready for prime time ? Maybe you're missing some very important during the development process: TEST !!!"

David Herron takes on the idea of providing an automated way of forcing developers to put Swing calls on the event-dispatch thread, in his blog
Re: Swing versus SWT Thread Confinement.
'I think, some of the frustration over Swing applications might stem from those who call Swing methods from outside the event dispatch thread, which then will have undeterminable behavior."

Finally, Michael Bouschen looks at
Java Persistence Query Return Types.
"The Java Persistence API (JPA) defines a query language that allows to define queries over entities and their persistent state. In this weblog I would like to point out what determines the type of the query result, such as the method to execute the query and the structure of the query SELECT clause."

The Java Today section starts off with a long-awaited JSR, as JSR 203, More New I/O APIs for the Java Platform (aka "NIO.2") is in its Early Draft Review. This draft, available for download, finally revises the filesystem API with a java.nio.filesystems package to add metadata awareness and a metadata-preserving copy method. The spec also adds asynchronous channels, the completion of the socket-channel functionality, multicast support, and buffer classes capable of containing more than Integer.MAX_VALUE elements. The review closes on May 27.

Among the many events at JavaOne this year (see the Java ME Guide to JavaOne 2007) the "Meet & Greet/Un-BOF and Bloggers Social" on May 9 at the Thirsty Bear restaurant is a chance for the diverse Mobile & Embedded Community to get together, socialize, exchange ideas, and give feedback. Terrence Barr's blog offers an information and a link to a wiki page to add yourself to the attendee list.

InfoQ takes a look at the new JRuby release in JRuby: Almost Ready for Primetime? "JRuby 0.9.9 is now out in the wild and has been declared 'ready for prime time'. The focus on this release has been compatibility with Ruby 1.8.4. However, despite compatibility being the overall priority, performance hasn't been ignored; JRuby 0.9.9 is 40% faster than the 0.9.8 release. One of the compatibility benchmarks the JRuby team uses is the ability to run Rails applications without errors, and this is something that they've finally achieved."

In today's Forums,
Hans Muller discusses the idea of a Swing timer service in
Re: JSR296 - Scheduled background tasks ?
"It's easy enough to create a Task that does some work periodically. The example below does some work on the EDT periodically. Creating a more elaborate API that allows one to schedule Tasks to run at absolute/relative times as well as supporting Tasks that are created and run periodically, is certainly possible. It's not part of the plan for the first Application Framework release."

Tim Quinn discusses a challenging deployment in
Re: relationship between two applications.
"Jan's comments about nested JAR class loading hit close to home for me. We have had a similar issue with app client support. To help support persistence units in app clients - and also as a way to resolve some other things - we had to alter the format of the generated app client JAR file so that it contains nested JARs. The app client must have the nested JARs in its class path, so the app client container must expand the app client JAR into a temporary directory (which is marked for delete-on-exit). The JARs in that resulting temp directory are no longer nested so they can be added to a class loader's class path routinely."

Joe Bowbeer would like to find the
Best handset for MIDP hobbyist.
"My full question is: Can MIDP hobbyists develop full-featured MIDlets and run them on their own handsets? By "full-featured" I mean having the ability to capture snapshots, play audio clips, and access the memory card and the network. (Without, that is, being prompted for approval every time; ask-once is enough.) By "hobbyist" I mean someone who either cannot afford a signing certificate, or cannot get one -- because after all they're only a hobbyist. Is there any handset, compatible with any carrier anywhere in the world, that satisfies these conditions?"

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 big JavaOne crunch, or 50 little crunches?