Skip navigation

We had an expert group meeting for JSR-314-EG today. The goal of the meeting was to make process on the issues in our issue tracker of record at <>. Before the meeting, I took each of the issues in the current issue tracker, styled with the winning XSLT stylesheet and put them into 7 roughly equal buckets. I chose seven "issue captains" from the JSR-314 EG and Mojarra team and made each one responsible for "understanding" the issues in their bucket. That meant I could ask various questions to the group of issue captains and expect reasonably informed answers.

An hour before the meeting started, Ryan, Roger, Jim and I spent some time removing duplicates from each of our own issue captain lists. During the first 30 minutes of the meeting, we went through my issue captain list and removed duplicates. The process used in both cases: the "current" issue captain would reach each of their issues and the rest of the issue captains present would have to speak up if one of their issues was a clear duplicate of the "current" issue. The current issue captain would also make an assesment of whether or not the issue should be closed outright for any reason (FIXED, WONTFIX, etc). After 30 minutes of this, we gave up and moved on to the next exercise.

After the obvious duplicates were removed, I asked each issue captain to list their top five or so issues from their bucket list only that they would like to see addressed. This took about 50 minutes. With the remaining time, I asked each issue captain to give me their top five "easy" issues.

Here are some issue tracker queries with our results.

open issues remaining after this meeting: 180

issues resolved at this meeting: 59

Hey, if you're here because you're interested in JSF 2.0, check out this fun video about how glassfish is better than WebLogic and cheaper too., or visit <>.

Technorati Tags: edburns

I'm happy to report that Ryan Lubke has committed the code that was previously being maintaned on the JSF_2_0_0_from_HEAD_20080606_BRANCH in the facelets cvs repository into the trunk of the Mojarra svn repository. This will allow us to continue to the work of integrating the feature set of Facelets into JSF 2.0.

I received three submissions to the contest. This is about what I expected given the amount of publicity I gave it (zero, aside from just posting the blog) and the difficulty of the task (not too hard, but non-trivial for most). I'm very happy with the submissions.

The winning submission was picked by the following criteria:

  • How well does it print? Does it print exactly one or exactly two issues to a page?

    How well can the output be used in the SCRUM meeting next week?

  • Am I satisfied with the information included in the printout of each issue by default?

  • How easy is it to modify the solution to reveal different information?

After carefully judging the entries I'm happy to report that Imre O?wald's entry is the winner! It was very tough to judge between Imre's submission and the runner-up, from Oliver Becker. In the end, I liked how Imre's looked. He had the priorities called out really nicely.

Imre, please contact me via email and we'll discuss how to get you the prize.

Thanks Oliver and arock392 for taking the time for the submissions!

ADDITION: Here is what the current state of open JSF issues looks like rendered with Imre's stylesheet:

Technorati Tags: edburns

Taking a cue from the success of the community that has grown up around the JSF IRC channel, my colleague and friend Rajiv Mordani has created an IRC channel for the entire Glassfish WebTier, on freenode.  To access the channel, follow the instructions for the JSF irc channel but use #glassfish-webtier as the channel name, instead of ##jsf.

Here's an inside tip: Rajiv is also the spec lead for Servlet 3.0.  If you have any gripes or feature requests for Servlet 3.0, Rajiv himself can often be found on the channel.

I'll be there to, and I hope to see you there!

  Technorati Tags: edburns

We've been working on JSF 2.0 for over a year now and we're very close to having solid specifications and implementations for our top two issues: Ajax and EZComp. Of course, the implementation of both of these issues has required lots of work on smaller issues.  However, at least 80% of the features people want to see in JSF 2.0 are not touched by Ajax or EZComp.  To help us prioritize the issues, I'm having a contest.

The first person to give me a tested and working XSLT stylesheet (and instructions on how to use it) that styles an XML export of the issue tracker issues will be sent an autographed copy of my new book Secrets of the Rock Star Programmers.  You'll have to paypal me the shipping and handling cost.  The winner can tell me how fast they want it and the costs will be calculated from there.

The winning stylesheet must meet at least these requirements.

  1. It has to be able to style this        xml file (and others like it).

  3. The result of running the style sheet on the XML input        must be something I can easily print (HTML or PDF, for        example).

  5. The printed output should have exactly one        issue tracker issue per page.  I have some links        on how to do this in HTML at <>


You get a special bonus if you can tell me how to easily and cheaply print these on 5"x7" index cards.

I plan to use this printed output to do a scrum-like feature prioritization exercise.

The contest will close next Tuesday, 12 August 2008 at 23:59 EDT.

Please send your entries to me via email to "ed dot burns at sun dot com", and put "ACTION: XSLT CONTEST" as the subject.

  Technorati Tags: edburns

Filter Blog

By date: