Skip navigation

The analysis of the recent Amazon EBS outage has been posted on the AWS blog [1]. I read it and was incredibly impressed with the detail, depth, clarity and competency shown. Of course, they need to impress the users with those things because they're asking us to trust them with our crown jewels. Even knowing that they are in the business of instilling confidence, it's clear the AWS team has their act together.

The document explains exactly what went wrong, why it went wrong, and lists detailed steps they say they will take to fix it. Their approach to resolution has several dimensions: ranging from technical to human communication, to education. (If only the Final Report on the Investigation of the Macondo Well Blowout was so clear on the steps to take to prevent failure. [3]) On the education front, you may be interested to know that Amazon knows that developer education is a key element to building their platform. As such, they are offering a webinar series, starting Monday 2 May, about making it easier to take advantage of multiple Availability Zones. You can see the schedule at [2].

 [1] http://aws.amazon.com/message/65648/  [2] http://aws.amazon.com/architecture/  [3] http://ccrm.berkeley.edu/pdfs_papers/bea_pdfs/DHSGFinalReport-March2011-tag.pdf

Technorati Tags: edburns

Two Thursdays ago, I called for the community to vote for their top five issues, you responded with 186 votes, the results of which are captured in JIRA filter JSF_2_2_VOTED_ISSUES and in the following chart.

Bar chart of issues and the number of votes for each

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.

As spec lead, I am now preparing a proposal for a work plan to attack these issues in the time we have alotted for JSF 2.2 development. This plan will be shared with the EG and will be the subject of our next EG meeting.

Technorati Tags: edburns

No, I'm not talking about implementing a Logo JSF RenderKit.  I'm talking about a little image that can be used to represent the JSF specification on slides, web-sites, T-Shirts and such. JSF has been around for ten years now and still doesn't have a logo.  As Dan Allen has repeatedly said, it's past time for that to change.  This blog entry announces a contest to make a logo for JSF.  The winner of the contest will get a free signed copy of my book, "Secrets of the Rockstar Programmers", if they want it.  International submissions may have to help with shipping, depending on how expensive it is for me to ship the book to them.  I wish I had a more compelling prize, but that's the best I can do.

 

The reason JSF does not have a logo thus far is that corporations treat logos as IP that must be protected, and that implies legal consequences.  As such, the winner must submit a signed Oracle Contributor Agreement per the instructions in the FAQ

 

Please submit your entries by attaching them to JIRA issue <http://java.net/jira/browse/JAVASERVERFACES_SPEC_PUBLIC-980>. The contest closes on 29 April 2011 at 12:00 pm Eastern Daylight Time (GMT-5), at which point I will look at the submissions and pick the winner.

As mentioned earlier and elsewhere, JSF 2.2 is getting started right now. This blog entry is a call for serious, committed participation in the JCP Expert Group dedicated to delivering that specification.

Ever since Oracle acquired Sun Microsystems and Java, there has been criticism of their handling of community and JCP. Some have gone so far as to say that Java is no longer free as in speech, and that JCP stands for "just customers please". I'm here to tell you that, as with most sweeping generalizations, your mileage may vary. The JCP affords, and Oracle management allows, their spec leads wide latitude in how they want to run their expert groups. Under JCP, spec leads can be as open as they want, as long as some minimum level of open-ness is met. As long as I've been running the JSF expert group, we've been very open. In fact, since March 5 2009 the JSF expert group mailing list has been publically readable, and even before that I've been very willing to accept EG nominations from any qualified individual or organization. This will continue to be the case for JSR 344.

If you are serious about contributing to the Expert Group, have your employer join JCP, or you can join as an individual. Once you have joined JCP and your JSPA is on file, fill out this form to nominate yourself to join the Expert Group. Expert Group members are expected to contribute at least three hours a week to constructively participating in developing the spec, mainly via the mailing list, but sometimes in teleconferences and via tasks I delegate to group members.

If full EG membership is not your cup of Java, you can observe the expert group discussion list by subscribing to users@javaserverfaces-spec-public.java.net. You must first join java.net, which you can do at <https://java.net/people/new> (yes, it's a JRuby on Rails app). The welcome email on the observer's list includes a link to the JSR-344 welcome email, which contains a wealth of information about how the Expert Group is run. Particularly useful is the link to the issuetracker of record for the EG, <http://java.net/jira/browse/JAVASERVERFACES_SPEC_PUBLIC>.

Technorati Tags: edburns

Filter Blog

By date: