In Relation To

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

Gavin pointed out to me that my script to build the Weld distribution was broken, so I've create Weld 1.0.0 SP1 (Service Pack 1) which remedies this. You can now find Weld's sources and binaries in artifacts/weld and the CDI API source, javadoc and binary in artifacts/cdi. Download it from here.

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.

I'm pleased to announce the release of Weld 1.0.0 - the announcements have been flowing in over the last few days, but this is my favorite!

Mark Little, the CTO of JBoss, blogged about our vision for component models in JBoss platforms - he gives a great overview, describing how Seam (and JSR-299/Weld) will form the core programming model.

Today, Red Hat submitted the final draft of JSR-299[1], which now goes under the moniker CDI (Contexts and Dependency Injection), along with the Reference Implementation and TCK. Check out the spec[1] and Javadoc.

I just noticed that CDI makes it possible to write properties files in Java, instead of plain text. I'm not sure if this is useful, but it is cute.

I put a whole bunch of work into the Javadoc for CDI recently. You can see it here. There's a good overview of the spec in the package doc for javax.enterprise.inject.

I'm trying really hard to emphasize to the community that CDI and Weld are not just a dependency injection solution. We did not come at this from the point of view of trying to solve dependency injection, or of trying to build a better Spring.