JavaOne comes around again...in May this year. The track category "Cool Stuff" promises to be innovative and eye-opening. You can check out the planned Cool Stuff sessions.
Curious about the Mustang Collaboration effort, I decided to give it a try. Sun is a big company, they're asking for public collaboration on a huge software project, and I wondered if public submissions would actually find their way into the product.
The Java platform has come a long way in its effort to minimize the difference between the performance and integration of native applications and Java applications.
In route to their final storage destination on the World Wide Web, characters move through various layers of programming interfaces and can cross software and hardware boundaries.
After coming out of holiday hibernation, Sun shows signs of integrating the bug fix I contributed late last month. I received an email thanking me for the fix. Brief, but containing everything I wanted to know, the email is below:
After so long anticipating this moment, after the deed is done, I feel like it was too easy. I'm definitely experiencing an anticlimax.
After a brief rest from this public Mustang community experiment, I'm back. And I've found the perfect bug...it's easy to fix, very low hanging fruit that's just right for a new contributor to Mustang. What is it? It's bug/change request id #4994762, and I'm all over it.
It's relatively easy to enter multilingual text into a rich client, Swing application. Doing so in a browser-based, web application isn't always as easy.
Hands on labs were quite popular at JavaOne Tokyo. This particular lab taught how to use EJB 3.0. Many of the labs were filled to capacity.