I am very pleased to announce the release of Weld 3.0.0.Final - the first implementation of CDI 2.0! I would like to thank not only to everyone involved in this particular release but also to the Weld community as a whole and also to all active CDI EG members who invested a lot of energy into the specification process! [ source, java ] /** * TODO: Continue to deliver bugfixes and improvements */ public class WeldTeam extends...

Even as we get ever closer to CDI 2.0 final version, we shan’t forget about our stable 2.4 branch. Ladies and gentlemen, here comes the next-in-line 2.4 release - Weld 2.4.3.Final! Notable fixes and improvements: Weld now shares proxy classes for built-in beans of the same type (WELD-2344) Fixed usage of Jandex on Tomcat when using unpackWars=false (WELD-2357) Weld now supports wider...

I am very pleased to announce the release of Weld 3.0.0.CR2 (CDI 2.0-PFD). The intention is to provide the latest updates so that early adopters and reviewers can work with up-to-date reference implementation during the JCP review process. Notable fixes and improvements: InterceptionFactory handles interface correctly (WELD-2335) Enable to obtain InjectionPoint metadata from within BeanConfigurator#produceWith() (WELD-2333) ObserverMethodConfigurator.beanClass() should be preset to the extension class...

As you may know, CDI 2 (JSR 365) is in Public Review phase. That’s great news for early adopters. But for now, I am very pleased to announce another production-ready version of Weld 2.4 (CDI 1.2). See also the release details. Thanks to everyone involved in this release! Warning There is a regression in Weld 2.4.2.Final. The problem only occurs if a Security Manager is used. However...

Contents Using Weld in JUnit tests Arquillian as the chosen framework for testing Java EE application server Servlet environment Java SE environment Arquillian Weld Embedded container In this follow-up article of our Weld Tips series we are going to focus on testing of CDI/Weld applications. Let’s discover options for unit testing in the first part and then continue with integration testing. To set things straight - by integration testing we mean testing...

I am very pleased to announce the release of Weld 3.0.0.CR1 (aligned with CDI 2.0-PFD). See also the release details. Thanks to everyone involved in this release! This version of Weld will be part of the JSR 365 Approval Ballot (watch CDI spec website for news). The Beta1 version of Weld 3 turned out to be sufficiently stable and so the first release candidate is mostly dedicated to cleanup and...

I am very pleased to announce the first Beta version of Weld 3.0.0 (CDI 2.0). See also the release details. Thanks to everyone involved in this release! This is an important milestone. CDI 2.0 is now considered "feature complete" and so the next Weld 3 versions should be mostly dedicated to cleanup and optimization. The next version will be Weld 3.0.0.CR1 (ETA in mid January). Finally, we would...

The development of Weld 3 (CDI 2) is underway. However, we don’t forget about the maintenance of the stable branch of Weld! So I am very pleased to announce the first bugfix version of Weld 2.4 (CDI 1.2). See also the release details. Thanks to everyone involved in this release! Notable fixes and improvements: removed false positive warning about Jandex version used (WELD-2231) fixed Groovy support - only filter out relevant...

Contents Bootstrap Discovery mode Extensions Jandex Runtime Identify problematic components easily Lazy initialization of bean instances Drawbacks of @Dependent pseudo-scope Mapping CDI contexts to HTTP requests Bean identifier index optimization In this article we’re going to dive into various performance aspects of CDI applications. As you’ve probably noticed performance testing is sometimes tricky. First of all, it’s difficult to create a meaningful benchmark. One should understand the JVM...

Contents How to enable the development mode Web application WildFly Weld SE How does it actually work? Probe UI What if I don’t have a webapp? Does it work offline? In this article we’re going to cover the special mode for application development. When enabled, a built-in tool called Probe provides a detailed insight into internals of a CDI application. Probe makes it easy to inspect: bean archives beans and...