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/.
Over the last year or so, we've been thinking hard about what kind of
new functionality we want to see in the next rev of the EE platform,
and feeding our ideas to Sun to incorporate into the JSR proposals
for the next round of EE specifications. These JSRs should become
public fairly soon now, but I wanted to give a rundown on the things
that are important to me, and why I think they're important. A lot of
these items have come out of our experience with Seam, others have
been things that have been missing from the platform for a long time.
My wishlist is pretty long, so I'm going to spread it over several
posts. First up, I'll talk about session beans.