Blogs by topic Web Applications and user edburns

I'm ashamed to say it, but we've gone over two years without having a working nightly build system for Mojarra. As of last week or so, I finally got the nightly working again. We now have our internal hudson instances configured to publish nightly SNAPSHOT builds to the java.net snapshot repository.

If you want to try out the absolute latest Mojarra 2.2-SNAPSHOT, you can run it on GlassFish 3.1 or GlassFish 3.1.1. To install it, grab the 2.2.0-SNAPSHOT version of Mojarra from this repository.

You can see that JSF+CDI and multi-component validtion are the two big winners, followed by resource handler improvements and a feature that seems like taking the composite components to the next level: support for composite applications.

Help us organize our open issues for JSF 2.2 by voting for your top five issues.

I describe the hudson jobs for Mojarra and the automated tests run by those jobs.

 Mojarra 2.1.0-b11 will likely be the final release of 2.1.0.

 The Mojarra JSF Developer community can now know when it is safe to check in to the Mojarra source code repository.

I ask for people to share their thoughts on what wastes time during development with JSF.

At the very beginning of my full time programmer career, when I worked at Silicon Graphics, Larry Wall and Randal Schwartz gave a brown bag session about their now legendary camel book. Naturally, I had them sign my copy, the front page of which I proudly display at left. Notice the “There’s More Than One Way To Do It!” stamp at the top. For better or worse, Perl is famous for this property. Less famous (or perhaps even infamous) for having more than one way to do it is JSF. At the JSFdays conference last week, I was having lunch with a friend who is an experienced developer and the topic turned to JSF deployments in large projects. He mentioned that his project was bitten by the fact that there was more than one way to do it in JSF. If you give developers more than one way to do something, they'll take advantage of that capability. But, in a large project with many developers, this can lead to confusion and unmaintainability. The simplest remedy is to establish firm and strong conventions for how to do things for which there is more than way one to do it. Of course, this is easier said than done, but I believe, as do Wall and Schwartz, that having more than one way to do it is generally an asset rather than a liability.