What's your opinion of GlassFish Issue #1047? Oh, you haven't memorized all of our Issue Tracker entries? So an ID number with no other context is pretty meaningless? Well, you're probably not alone there. Vince's latest blog entry shows how to use Greasemonkey to customize how Firefox displays the Java.net Issue Tracker pages for GlassFish. So instead of a not-so-helpful title like "glassfish: Issue 1047," you can get one which includes the issue summary, like "#1047: version -verbose isn't verbose enough."

There are lots of options for tracing web applications. But suppose you need a holistic view, such as a combined trace of the server-side Java and client-side JavaScript in an Ajax app. You might expect your options to drop to zero. Well, they don't. DTrace can handle it. The Mozilla DTrace Project provides DTrace probes for Firefox's JavaScript engine, and recent versions of the JVM have built-in probes. Amit's latest article shows how to put these together to trace an Ajax application. It produces a true end-to-end picture, with traces flowing across the client/server boundary.

We are way past the feature brainstorming phase for GlassFish V2 but I think we should start thinking on how to do this for V3 and we may want to check how Firefox is doing it. Check this article in The Register and the Brainstorming Wiki Should we plan a similar approach for collecting ideas for GlassFish V3?