A tiny update for Weld 5 has just been released. We have identified a bug that EJC (Eclipse Java Compiler) users can encounter in combination with interceptors and lambdas in their beans and fixed it. This could, in certain circumstances, yield a very hard to decipher bytecode generation error. Note that never manifests when using standard javac compiler. For those interested, the details are in the WELD-2806 JIRA. [ Download ] [ Documentation ]...

A small update for Weld 5.1 (5.1.4.Final) has been released. List of changes from 5.1.3.Final version: Fix resource injection into beans added via extensions (WELD-2798) Prevent file leak in Weld’s ServiceLoader (WELD-2800) Note that most environments were unaffected by this; the only reported issue was for testing setup of GlassFish on Windows machines Deprecate WeldCrossContextFilter, to be removed in Weld 6 (WELD-2803) Update...

Since there have been no further bugs reported, Weld 6.0.0.CR2 has evolved into its Final form. Say hello to Weld API 6.0.Final as well as Weld Core 6.0.0.Final! Since there are no changes from the previous CR2 version, early adopters shouldn’t encounter any unwelcome surprises. Nonetheless, should you run into any bugs, do get in touch so that we can squash them as soon as...

Turns out we forgot to perform some code cleanup in the CR1 - so here goes 6.0.0.CR2 which removes deprecated code pieces. Note that Weld API is unchanged; the only deprecations there are changes coming in recent CDI versions so we’ve kept that code around for now. Resolved issues in this version: Revisit deprecated code in Weld Core (WELD-2804) Remove WeldCrossContextFilter (WELD-2803) As per usual, please report any issues...

First version of the Jakarta EE TCKs has finally landed in Central and with that, we have re-enabled all remaining TCK tests and are confident enough to issue a candidate release for Weld 6! Note that both, Weld API and Weld Core artifacts have been released. Here is the list of changes from last Beta: Implement validation for unproxyability of sealed types (WELD-2799) Correct injection into @Resource fields of beans registered through extensions...

A new version of Weld 5.1 has landed in Maven Central. This is a bug squashing round which backports several notable fixes and changes from Weld 6 into Weld 5: Change BeanManager resolution process for BuildCompatibleExtension not belonging to any bean archive (WELD-2794) LazySessionBeanStore no longer swallows exceptions happening when attempting to initiate HTTP session (WELD-2762) Correct how we determine proxy package for beans with unassignable types in their bean type set...

New versions of Weld artifacts are now available in Central - Weld Core 6.0.0.Beta4 accompanied by Weld API 6.0.Beta5. Where applicable, 6.0.0.Beta4 bumps up Jakarta dependencies to their Final variants as well as implements remaining features from CDI spec, adds new Weld-specific API and addresses multiple backlog issues that were scheduled for this major release. You might be wondering where did Betas 2 and 3 go. While...

Weld Core 6.0.0.Beta1 along with Weld API 6.0.Beta2 are the latest two artifacts you’re going to need if you’re looking for an implementation of the CDI API 4.1.0.Beta1. Changes based on CDI specification since last 6.x version: The method invoker API in CDI has been simplified and the transformer functionality removed from the specification (WELD-2765) Weld API introduced WeldInvokerBuilder which retains...

Looking for a CDI 4.1 implementation? We’ve got you covered! Weld Core 6.0.0.Alpha1 is now available and comes along with CDI API 4.1.0.Alpha1. Note that this version also uses latest version (2.2.0-RC1) of the Jakarta Interceptors specification. CDI/CDI TCK related additions: Create first implementation of CDI method invokers using MethodHandles (WELD-2764) If you want to read up more about the original...

Weld 5.1.2.Final has landed in Central and with it some new bufgixes. Here is a summary of the changes: Avoid creation of duplicated thread groups on application re-deploy (WELD-2755) This could lead to a very tiny memory leak on repeated app re-deploy while on app servers (such as WildFly) WeldInitialListener can no longer throw NullPointerException if the application failed to start properly (WELD-2752) WeldManager#getContexts not properly returns...