In Relation To

InfoQ has published a their questions and my answers about CDI and Weld.

One of the really nice things about Weld is how nicely it works in Java SE. Of course, if you run Weld on its own, you won't get nice functionality like EJBs (you'll need an embeddable EJB container for that), but you do get a bunch of great stuff, including:

A developer new to Java EE posted in the Weld forum asking for advice on getting started learning EE 6. I've decided to promote part of my response in the forum to the blog.

Here's a CDI portable extension that reads values from properties files and configures fields of Java EE components. In Java EE 6, this works for any Java EE component supporting injection, including servlets, EJBs, managed beans, interceptors and more.

One of the nicest features of CDI is the portable extension SPI. According to the spec:

In case you're like me, and you missed this when it was first published, check out Andy Schwartz's summary of what's new in JSF2. (Andy's one of the good guys on the JSF EG.) It's fun to compare the final product to my wishlist from back in '07. Oh, what innocent, carefree days...

William Drai has blogged about his experience integrating Granite DS and CDI.

I've written a couple of posts about using @Alternative to achieve deployment-time polymorphism. What I've never really talked about is its role in CDI modularity.

This is just too cool. That's a test coverage report. It doesn't report coverage of the RI code by the TCK. It reports coverage of the CDI specification by the TCK.

The question of backward compatibility is something that all framework developers wrestle with. The term means different things to different people: