Skip to main content

Running On Empty

Posted by editor on September 4, 2007 at 6:45 AM PDT

Tim Boudreau's NetBeans tour faces an unforeseen delay

You might have gathered from yesterday's blog that I've driven much of the I-80 route that NetBeans Evangelist Tim Boudreau is taking for his informal NetBeans tour / personal relocation. I did the midwest-to-SF back and forth three times overall in the 80's and 90's. And on one of those trips, a leaking coolant hose led me to drop into neutral and coast down the slope of a foothill in Nevada, somewhere between Wendover and Winnemucca, in hopes of getting enough air through the front grill to keep the engine from overheating. Again. I finally made it to a tiny service station, where I paid $40 to a passer-by who fixed the leak with a pocket knife. Filling up with a jug of coolant, I was able to make it to San Francisco two days later.

Moral of story: it's not a great route to take a vehicle that's in a dubious state of repair.

Tim's latest update is that he's Almost mobile, explaining, "I got the NetBeans Mobile loaded, and picked up a slew of NetBeans t-shirts, books, USB drives and squishy balls. And got all of 3 miles."

Unfortunately, I'm having some alternator trouble - and it's probably my own doing (baf! baf! ) - when I replaced the hot wire to the battery the other day, well the solenoid is above the transmission, in a tight spot where you pretty much do everything by feel. I suspect there is a wire I didn't reconnect :-( Driving by day you don't notice that all the electrical systems are running off the battery, and I'd assumed that the jump starting was simply the battery not having charged earlier. I knew I should have checked the current across the terminals with it running earlier!

Keep up with Tim's progress via Twitter and a rolling update page, and wish for good things or say a prayer for him or whatever... having smokily rolled to a breakdown at the base of a twilight foothill, that's not a route I'd want to take an old painter's truck on.

Also in today's Weblogs.
David Herron draws an analogy between
The Unix wars and Java compatibility.
"There was a little throwaway idea in my previous posting, Java is doomed to failure, which is growing on me. While writing I had this thought about the Unix wars.. and really that period, the fallout from which is still with us, is a great analogy of what could happen with Java if the various implementations were allowed to differ greatly."

John Catherino has nifty news in
Simple Inter-JVM communication... The Grail!
"Announcing a significant breakthrough from the cajo project in the area of dynamic co-operation between Java Virtual Machines. I'll bet you never thought it could be this easy."

The latest Java Mobility Podcast is
Java Mobile Podcast 17: JavaDB, a database implementation for all the Java plaftorms.
"Java DB is Sun's supported distribution of the open source Apache Derby 100% Java technology database. Rick Hillegas, Sun Senior Staff Engineer and Apache Derby developer, provides insights into uses of JavaDB, developing in a distributed environment and upcoming features in the next release of JavaDB."

In Java Today,

Kirill Grouchnikov has announced the release of version 4.0 of the Substance look and feel project. Substance 4.0 adds six new skins, state-aware theme transitions, smart tree scroll, glowing icons, support for JXPanel translucency, SwingX UI delegates in SwingX plugin, border painters, and new title painters. In his blog, Kirill also announced releases of Substance's sister projects: a new version 3.1 of Laf-Widget and version 2.0 of Flamingo.

Silicon Valley Web Developer JUG Lead Mike "Van" Riper has created a map with active JUGs worldwide, now hosted as part of the JUGs community. Each placemark shown on the map links to the JUG leaders and the JUG's home page. If you would like to add your JUG, send an e-mail to the jug-leaders mailing list. author Diego Adrian Naya Lazo has published a new book, simply titled OSWorkflow, on the eponymous workflow system from the OpenSymphony collection of open-source enterprise projects. The book introduces the basics of workflows and builds an example, then extends its functionality by integrating the Drools rule engine and the Quartz job scheduler.

In today's Forums,
osbald has some suggestions for the SwingX project in the thread
Re: What SwingX version I use?
"I'd still like to see the milestones vanish - it isn't entirely clear to me why swingx downloads are made available from - it's just another thing to keep up-to-date, or not. If we've not updated the milestones for a couple of years is it not time for a rethink? At the very least add a huge health warning and a link to the project pages. I tend to think the dev packs (and component shop) just confuse things further - unless they'res something I'm not getting here. While I'm on my high horse I'd like to see some movement towards 1.0 (possibly a branch to tackle JDK6/7 compatibility?), integration with appframework and beansbinding projects (although the latter's been in a sorry state for some months it seems). Bit worried JavaFX is going to steal the limelight and set things back a year or two."

ismafc reports success working with Mobicents recordings in
Re: Problem with Voicemail:DTMF receive and vmail file play back! "Working about this I've discovered an interesting thing and now I can play a previously recorded message. I've caught the recorded file, and using the Java class AudioSystem (javax.sound.sampled.AudioSystem), specifically the static method getAudioFileFormat, I do AudioSystem.getAudioFileFormat(fileRecorded); then I obtain that the file format is AU (.au). Now, if I record the file with .au extension instead of .wav I can play it (also simpy renaming the file and changing directly the extension). So, I think that the problem was that the media RA records in AU format, and so when you try to play the message the WAV Parser is unable to get the format because it's not the format."

Finally, lucretius2 offers a reality check on one of Java's notoriously unimplemented reserved words, in
Re: Will they ever implement the 'const' keyword? "sjasja took the words right out of my mouth. 'const' in C++ is lame - it makes a promise (that an object won't be modified) that it cannot in general fulfil. It just leads to a false sense of security, that makes you write code with bugs that are merely subtler than before. For instance, suppose a method is passed 2 parameters: Foo* x and const Foo* y. The method compiles because it modifies x but doesn't modify y. So y is always unchanged by the method? almost always - unless x and y point to the same object. Nasty bugs lurking... The situation is exacerbated by multithreading, when y could of course be changed at any time by another thread, despite its supposed constness."

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.

Tim Boudreau's NetBeans tour faces an unforeseen delay