Weld 3.1.2.Final is coming along with Weld API 3.1.SP1. It is another small release bringing in mainly bugfixes. One notable thing is that thanks to guys from Jetty, Weld 3.1.2.Final is ready to operate with lastest Jetty 9 as well as upcoming Jetty 10. Other than that we have tried to address some dodgy issues with possible race conditions and leaks - see for yourself! Fixes and improvements...

Weld 3.1.1.Final is out, it is a rather small nonetheless important maintenance release. There is bunch of fixes present here; notably one for context propagation API that could cause some headaches with context seemingly not propagating. Moving on, we also have some improvements to asynchronous events on default executors or ordering on ProcessAnnotatedType events. Fixes and improvements: Weld API/SPI Weld Core WeldAlterableContext#clearAndSet() was incorrectly leaving some caches behind (WELD-2566...

Weld 3.1.0.Final and Weld API 3.1.Final are now up for grabs. What’s in it for you? There are quite a few new things in the mix - InterceptionFactory improvements, new API clases and methods, improvements to class defining for integrators in preparation for JDK 12. We now also support CDI context propagation between threads; there is a whole new SPI that allows users and/or frameworks to propagate request...

Weld 2 has entered maintenance mode with its 2.4.7.Final release earlier this year. Now we are coming with a maintenance release containing fixes to several nuisances you might have come across. Notable fixes and improvements: Weld Core: Opt-in enhancement in HTTP session replication, more eager approach (WELD-1130) Note that WildFly does not need to use this AfterTypeDiscovery did not allow to remove declared interceptors/decorators/alternatives correctly (WELD-2479) Corrected...

Weld 3.0.5.Final is here and hand in hand with it comes Weld API 3.0.SP4. And in case you missed it, there was CDI 2.0.SP1 release as well. It comes with few security manager related fixes and Weld is of course compliant with it. If you are running on a servlet or in SE, you may need to update it yourself, in case of EE it usually falls to...

I’m pleased to announce a couple of changes coming to the Weld team. First of all, Matěj Novotný will be taking over the leadership of the project. Matěj has proven himself to be an excellent engineer, contributing not only to Weld projects but also to the CDI specification and TCK development. I’m really happy that I can hand over the leadership to this guy! Matěj’s primary...

Weld 3.0.4.Final is here along with Weld API 3.0.SP3 - make sure you update both. In this release we took first steps towards eliminating illegal access in JDK 10+. The good news is, Weld should now be able to run with --illegal-access=deny. The project and CI infrastructure around it went through a lot of changes to be able to build and execute on JDK 10 and there is still...

Weld 2.4.7.Final is now available. It includes multiple important bugfixes, many of them focused around proxy generation and/or invocation. Note Weld 2.4 now enters maintenance mode - there will be no further active development on Weld 2. We will be channeling our efforts into Weld 3 instead. Notable fixes and improvements: Weld Core: Proxy-related issues: Fixed possible NPE with multiple deployments one of which uses relaxed construction configuration (WELD-2448...

How do you cook Weld 3.0.3.Final? You start with a speck of bug fixes add some proxy generation improvements top it off with adjustments for integrators. Notable fixes and improvements: Weld Core Fixed invocation of private observer method in some very specific cases (WELD-2443) Container agnostic proxy serialization (WELD-2447) Improve shared proxy class instantiation for multiple deployments with relaxed construction enabled (WELD-2448) beans_1_1.xsd is now known to Weld...

Contents GAV Coordinates First Steps Dude, Where Is My Container? Help, I Am Stuck With JUnit 4 What If I Would Like To…​ In this article I want to bring weld-junit into light. You might have heard about or, better still, used our extension for JUnit 4 which has been around for some time now. But after getting ourselves acquainted with JUnit 5, we decided we should create another one for JUnit...