Tags
Authors
The recording of my CDI webinar from Wednesday (second highest attendance in the series, just pipped to the post by Bela talking about clustering!) is now available. Enjoy!
Why don't CDI beans have names by default?
We've decided to make a few changes to the leadership of the Seam and Weld projects, the reasons for which I'll outline in this blog post. First however, let me give you the headline changes!
I've just published a release candidate for Weld 1.1.0, the reference implementation of JSR-299: Contexts and Dependency Injection for Java EE. It's based on the CDI 1.0 API. You can find direct download links at the bottom of this post or you can pull the artifacts from the JBoss Maven Repository.
CDI support in EAP 5
Quite a few people have asked me recently if they have to wait until EAP 6 before they can use CDI in a supported JBoss application server. The good news is, no they don't! While there isn't currently any productised offering for CDI itself (i.e. it's unsupported), it is still possible to use it as the component framework for your EAP-based application thanks to the Weld-servlet library. What's even better is that it requires absolutely no configuration changes to the default EAP installation - CDI based applications can be deployed straight to it and will work out of the box.
Dan did a webinar yesterday looking at Java EE 6 and CDI, showing how it can be used to improve your application development.
Weld Extensions is a portable library (licensed under the ASL 2) providing utilities and common functionality for CDI applications and libraries or frameworks based on CDI alike. We'll be using it as the base of Seam 3. It contains extensions to the core CDI programming model, typed logging (courtesy of JBoss Logging 3), managed resource loading and support for evaluating EL anywhere.
