In Relation To

The Web Beans event bus provides a very nice way for stateful components to synchronize their state with changes that take place in the application.

The public draft of the JPA 2.0 specification is already out and includes a much-awaited feature: an API that lets you create queries by calling methods of Java objects, instead of by embedding JPA-QL into strings that are parsed by the JPA implementation. You can learn more about the API proposed by the public draft at Linda's blog.

Over the past few weeks, we've had a number of conversations between the major Java EE vendors regarding the inclusion of Web Beans (JSR-299) in the Java EE 6 platform. Several members of the EE 6 expert group have concerns about how the current draft of the specification characterizes the functionality of Web Beans, and about how well the functionality integrates at the platform level. Therefore, as requested by one of the other vendors, we've extended the Public Review period until early February with the goal of taking further input from folks with platform expertise. The expert group will submit a revised Public Review Draft in late January or February that incorporates this feedback.

I keep getting asked about the relationship between Seam and Web Beans. At a high level, the mission of the Seam project remains unchanged: to provide a fully integrated development platform for building rich Internet applications, based upon the Java EE environment. In Seam2, this platform consists of the following layers:

I want to say something about the Panasonic DMC-LX3. I've never written a camera review before, but I'm so inspired by the fact that finally someone made a compact camera for people who actually know something about photography, that I want to do something to encourage this trend.

Something that's always slightly bemused me is that software development methodology is something you never seem to hear discussed in organizations whose business is technology. Sure, product companies are certainly very interested in practices and tools to support good practices. (For example, product companies certainly care about testing practices.) But technical practices are kinda orthogonal to methodology debates. And I never hear about a company like Red Hat paying any attention at all to the latest fashions sweeping through the world of agile consultants and project managers. In fact, I'd be very interested to hear of a single example of a truly great software product that was developed (at least initially) according to a methodology.

Here's another usecase for the injection point metadata API that we're considering adding to Web Beans. I've always thought it would be nice to be able to inject entity instances by role, instead of passing references around the system. (In Seam, you can use home objects to achieve this.)

In the comments thread for this post, Bill got me thinking again about a problem that's been bugging me for a while.

It's fun to see what people are using Seam for:

IntelliJ IDEA 8 has Seam support. Cool!