In Relation To

/This is the fourth installment of a series of articles describing the current status of the Web Beans specification. Please read the first, second and third installments first./

/This is the third installment of a series of articles describing the current status of the Web Beans specification. You can find the first installment here and the second installment here./

/This is the second installment of a series of articles describing the current status of the Web Beans specification. You can find the first installment here./

We're now really close to releasing a Community Review Draft for Web Beans. The purpose of the draft is to gather feedback on the component model, dependency management model and extensible context model that we've defined, and hopefully get people excited about Web Beans. We also need to get our work in front of the other EE6-related expert groups, so that they can start thinking about how they can possibly re-use and integrate with some of the mechanisms we have defined. However, the specification is by nature written in highly technical language, so this blog entry is the first in a serious of articles giving a friendly, introductory guide to Web Beans. When the Community Review Draft is released, please take the time to download and review it. But please read this series /first/.

Tomorrow (Wednesday) morning at 9:30, Bob Lee and I will talk about the work in progress on JSR-299. Over the last couple of months, we've been working with the rest of the Web Beans expert group to create a component model that combines the best of Seam, Juice, JSF and EJB 3.0. The end goal is the definitive programming model for business logic components in Java, combining Seam's state management with Guice's typesafety.

The Web Beans JSR was approved unanimously by the JCP executive committee. You can read the proposal here:

The recently finalized Java EE 5 platform dramatically simplifies development of Java applications.