Here we are with yet another small update to Weld 6; say hello to Weld 6.0.2.Final.
Changes in this version:
As always, do report any bugs you encounter so that we can squash them as soon as possible!
[ Download ] [ Documentation ] [ Release notes ]
First small update for Weld 6 has landed in Central.
There are only two notable fixes here, so let us take a look at them:
Fixed a bug that EJC (Eclipse Java Compiler) users can encounter in combination with interceptors and lambdas in their beans (WELD-2806)
This could, in certain circumstances, yield a very hard to decipher bytecode generation error.
Note that this does not manifest when using standard javac compiler.
If you are interested in more gory details, they are in the issue and/or pull requests linked to it.
Make ElAwareBeanManager injectable as a bean type
Inability to perform this was an oversight as it is a requirement in Jakarta EE WebProfile specification.
As always, do report any bugs you encounter so that we can squash them as soon as possible!
[ Download ] [ Documentation ] [ Release notes ]
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 ] [ Release notes ]
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 possible!
And speaking of getting in touch, we recognize that JIRA can be a little daunting, so we are trying to make that easier by enabling GitHub discussions. You can now ask your question in:
And don’t you worry, the weld-dev mailing list is still kicking plus, for the time being, we are still using JIRA for per-release issue tracking.
[ Download ] [ Documentation ] [ Release notes ]
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 custom TCK exclusion list used for relaxed mode testing (WELD-2806)
[ Download ] [ Documentation ] [ Release notes ]
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:
As per usual, please report any issues you discover with this release so that we can squash those bugs.
[ Download ] [ Documentation ] [ Release notes ]
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 (WELD-2798)
Improve the algorithm that determines BeanManager instance for synthetic beans coming from build compatible extensions (WELD-2794)
Weld OSGi bundle now correctly exports org.jboss.weld.util.reflection (WELD-2793)
Weld OSGi bundle now contains imports for built-in bean proxies (WELD-2796)
Re-introduce Jakarta EE CDI TCK into continuous integration (WELD-2778)
The TCK artifact in Central is not yet final (it is M1) but it is enough to make sure Weld passes all related CDI tests with WildFly
Fix possible file leak in org.jboss.weld.util.ServiceLoader (WELD-2800)
This was only reported during GlassFish testing and affected just Windows machines
Resolve license conflict of jboss-logging-processor inside shaded Weld SE JAR (WELD-2795)
As per usual, please report any issues you discover with this release so that we can squash those bugs.
[ Download ] [ Documentation ] [ Release notes ]
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 (WELD-2763)
This was only problematic in environments using WeldDefaultProxyServices to define their proxies (such as Weld SE)
Correct CommonLogger to mention correct GAV for Jandex (WELD-2770)
Added the ability to register Build Compatible Extension in Weld SE without discovery (WELD-2772)
Correct inheritance of producer fields if there is an extension present (WELD-2773)
Make sure @Default qualifier is added to events fired via BeanManager#getEvent() where appropriate (WELD-2775)
Observer method confiurator now correctly allows to override Reception settings without changing its notify() method (WELD-2786)
Clean up legacy Jetty integration parts (WELD-2787)
Use Lock instead of synchronized within ContextualInstanceStrategy to be more virtual thread-friendly (WELD-2788)
Skip superclass declarations of final methods when creating proxies (WELD-2785)
Ensure OSGi bundle has access to all dependencies needed for built-in beans (WELD-2796)
[ Download ] [ Documentation ] [ Release notes ]
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 you can find their artifacts in Central, they bear no difference from Beta4 apart from not having separate distributable ZIP and docs.
With that in mind, below is the list of changes since Weld 6.0.0.Beta1:
Added the ability to register Build Compatible Extension in Weld SE without discovery (WELD-2772)
Use Lock instead of synchronized within ContextualInstanceStrategy to be more virtual thread-friendly (WELD-2788)
Skip superclass declarations of final methods when creating proxies (WELD-2785)
Observer method confiurator now correctly allow to override Reception settings without changing its notify() method (WELD-2786)
Correct CommonLogger to mention correct GAV for Jandex (WELD-2770)
Invoker API enhancements (WELD-2780)
Proper exception handling
Document API Weld offer above what CDI specification has; Weld retains all parts of the initial design CDI had
Added benchmarks to have a measure of our implementation versus direct invocation
Code cleanup and other minor tweaks
Remove SecurityManager related code from Weld (WELD-2789)
SecurityManager has been deprecated for quite a upcoming JDK versions plan to remove it completely so we remove it as part of the major release version
This means Weld 6 no longer uses priviledged actions to perform various tasks, such as constructor invocations, reflection on classes etc.
Remove WARN logging when an interceptor binding target of lifecycle interceptors targets anything other than TYPE (WELD-2790)
Revise Weld 6 examples; only keep essentials (WELD-2771)
Address Weld API javadoc warning (WELD-2779)
Revisit servlet setup and testing (WELD-2784)
Clean up legacy Jetty integration parts (WELD-2787)
Note that the latest documentation incorrectly states that it is for SNAPSHOT which isn’t the case.
It is built for Beta4 but due to incorrect script setup the version number wasn’t picked up properly.
This will be corrected for the next release.
As always, if you find further issues with Weld 6, let us know and we’ll try to help.
[ Download ] [ Documentation ] [ Release notes ]
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 all of the transformers/wrappers that were originally present
We also added some more validation and other tweaks but the whole functionality is still being worked on as part of the follow up release
Support declaring @Priority on producers (WELD-2768)
This is also one of the features added by CDI API 4.1 and Beta1 of Weld supports it
BeanManager implementations in Weld now correctly extend ELAwareBeanManager from newly introduced CDI API module (WELD-2769)
There is no functionality change, this is just a step forward towards removing EL dependency from core CDI
Implemented programmatic access to assignability rules on BeanManager (WELD-2774)
BeanContainer/BeanManager now allow users to invoke #isMatchingBean() and #isMatchingEvent() methods
Other changes and bugfixes:
Correct inheritance of producer fields if there is an extension present (WELD-2773)
Make sure @Default qualifier is added to events fired via BeanManager#getEvent() where appropriate (WELD-2775)
Weld SE - manually registered portable extensions now reside in synthetic bean archive instead of their own (WELD-2776)
Updated CI setup to make sure bulk of our tests is running against JDK 21 (WELD-2777)
As always, if you find further issues with Weld 6, let us know and we’ll try to help.
[ Download ] [ Documentation ] [ Release notes ]
