Skip to main content

Hitsville, UK (and Germany, Japan, Israel...)

Posted by editor on April 27, 2006 at 8:41 AM PDT

The international search for bugs

Briefly noted in the results of the Mustang Regression Challenge, which sought out the best regression bug reports for Mustang (Java SE 6), is the international nature of the particpation. The results page lists the top five submissions, as chosen by JDK senior staffers, along with another five honorable mentions. Take a look at the sources of the submissions: Japan (three times), Germany (twice), United States (twice), Israel, Switzerland, and the United Kingdom. That's a powerful statement about Java's strong following around the world and the interest generated by the regression bugs contest.

Another thing that's remarkable is that despite the predominance of enterprise topics in many Java pursuits, most of these bugs concern desktop functionality: Swing, AWT, SWT, and Java2D. Granted, maybe that's where most of the heavy lifting is in Java SE (as opposed to EE), but to have quality bugs filed on the desktop technologies is an interesting and important reminder of how many people work closely with those technologies.

Congratulations to the winners of the contest, who will be receiving Ultra 20 workstations for their efforts.

Also in Projects and
five years after its launch, JXTA "has moved from being only a prototype to being the industry-leading open-source peer-to-peer (P2P) technology for use in large-scale implementations." The SDN article JXTA Technology Turns Five Years Old looks at the industrial applications of JXTA, its community acceptance, the technical enhancements made to the standard, and the potential for its future.

Our Feature Article discusses Using Dojo and JSON to Build Ajax Applications.
"The AJAX developer faces a series of challenges in his or her work: not just on the client or server side, but also in combining the two. Zarar Siddiqi suggests one combination that solves a lot of problems: using the Dojo JavaScript library and the JSON library for converting Java objects to and from String representations."

Swing Hacks goes East in today's Weblogs. Joshua Marinacci writes, "One of my co-workers from Japan, Yuka Kamiya, just told me that the Japanese translation of Swing Hacks is coming out this week. She blogged about it here, and while I can't read any japanese I'm pretty excited."

The World's Slowest Web Service, Chris Campbell asks:
"What happens when a client-side guy dips his toes in the river of web services (JAX-WS)? Come for the absurdity, stay for the tutorial."

Ethan Nicholas has been
Leaking Evil:
"I just ran into a wicked memory leak in Java 5.0. If you aren't aware of this one, you probably should be."

In Also in
Java Today
Frank Sommers writes
"Continuous integration assumes that the code builds cleanly on the integration server. While in principle no developer would wish to check in code that breaks the build, in practice build failures still happen. Slava Imeshev, whose company, ViewTier, provides a build automation tool, studied build problems, and found that most build problems emanate from a handful of development anti-patterns (patterns of what not to do)." In the Artima discussion Three Build Anti-Patterns, Sommers reveals these three anti-patterns: "Five o'clock check-in", "Spoiled fruit", and "It's a small change".

In the latest installment of the Java Posse podcast, episode 49, Posse members Carl Quinn, Tor Norbye, Dick Wall, and Joe Nuxall cover feedback to listener mail, discussing a proposal to make class members final and private by default, talk up the idea of XUL-based "thinlets", consider a JavaWorld article advocating the use of annotations to eliminate getters and setters, and, inexplicably, get onto a sidetrack about the infamous "Leeroy Jenkins".

In today's Forums,
sateh asks about

Developing with Maven 2.0:
"Does anyone have a simple Maven 2.0 project that shows how to do JEE5 development with glassfish?"

swpalmer clarifies the point of asking
Will JFileChooser ever get fixed on Windows?:
"Why don't I just write my own version of every class in the JRE that has bugs and forget that Sun has anything to do with it? :) I know I can work around the problem, that's obvious and has little to do with Sun fixing what's broken. Sun could just not fix any bugs - we can all just work around everything by writing our own code from scratch. The Swing team is a little more responsible though.. they actually fix their own bugs :) . But some are easier than others, sometimes it could be that there is no practical solution and that's that. My point being, that I was asking about JFileChooser and if I should expect improvements to be coming from Sun or not."

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