Weld 2.1.1.Final was released. More than 20 issues were addressed in this release. See the release notes for details. Thanks to everyone involved in this release!
[ Distribution ] [ Release notes ] [ Documentation ] [ CDI 1.1 Javadoc ]
I am pleased to announce that Weld 2.1.0.Final has just been released. Weld is the reference implementation of Contexts and Dependency Injection for Java EE (CDI). Here is the highlight of what’s new in Weld 2.1.0:
OSGi support with Pax CDI
Improved runtime performance and memory consumption
Better integration with various Servlet dispatch types
SLF4j was replaced with jboss-logging
30 fixed bugs
Weld-osgi is a framework that allows the CDI programming model to be used in the OSGi environment. The framework was developed entirely by the Weld community and became a part of Weld since version 1.2.0
The framework provides three main features:
The CDI programming model can be used within OSGi bundles.
The OSGi service layer and utility facilities are accessible through CDI injection
The CDI event bus can be used for both inter-bundle communication and delivering OSGi events.
The weld-osgi framework served as an inspiration for a standardization effort, known as RFC-193 (formerly RFP-146). The proposal is now part of the OSGi early draft
Due to the tight schedule of CDI 1.1, weld-osgi did never make it to Weld 2.0 and was therefore left behind, stuck in the gradually abandoned 1.2 branch.
In the meantime, work on the reference implementation of RFC-193 begun. The reference implementation is known as Pax CDI and it is an open-source project hosted on GitHub. Pax CDI aims to be portable across OSGi implementations as well as CDI implementations.
We always wanted to bring OSGi support back in Weld 2.1. However, we decided not to revive the weld-osgi framework nor align it to the new RFC-193 specification. Therefore, weld-osgi will not be merged into Weld 2.x code base. Instead, we decided to shift our focus towards Pax CDI and make sure it works well with Weld. This was done and Weld 2.1.0 is now one of the CDI runtimes supported by Pax CDI. You can play with the current Pax CDI SNAPSHOT or wait for the upcoming 0.5 release.
EDIT 2013-10-30: Pax CDI 0.5.0 was released. See the release announcement for more details.
The CDI specification requires the request, conversation and application contexts to be active during every HTTP request. Obviously, the CDI contexts are not necessary for every HTTP request. Fetching a static resource is an example of one such request.
In Weld 2.1.0 we optimized the component that handles context activation/deactivation and cut down the overhead. In addition, it is now possible to completely suppress CDI context activation on certain types of HTTP requests should this minimized overhead still be undesired. See Martin’s blog post or the reference documentation for more details.
We greatly appreciate your contributions to this release. Big thanks go to: Martin Kouba, Matúš Abaffy, Matej Briškár, Marko Lukša, Stuart Douglas, Marek Schmidt, Ron Šmeral, Tomáš Remeš, Max Pimm, Jesse McConnell, Harald Wellmann and Dirk Strauss.
[ Distribution ] [ Release notes ] [ Documentation ] [ CDI 1.1 Javadoc ]
A tip how to configure a new feature introduced in Weld 2.1.0.Beta2 which allows to skip CDI context activation for some HTTP requests: http://goo.gl/PAiwBS
Weld has a new web site and it’s built with Awestruct!
Weld 2.0.1.Final has been released. This is mainly a bug-fixing release with 20 issues fixed since the previous one. For details, see the release notes.
Our focus is now shifting towards WildFly and its Weld integration in order to provide a CDI 1.1 compliant container. For details about CDI 1.1, see Pete’s blog post. Furthermore, we plan frequent releases of Weld to continue, so expect another release in early July at the latest!
[ Distribution ] [ Release notes ] [ Documentation ] [ CDI 1.1 Javadoc ]
