Weld: News

Weld 5.1.2.Final

2023-10-5 release Matej Novotny

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 empty collection when there is no context for given scope (WELD-2761)
Fix client proxy creation for @Typed beans with package-protected types (WELD-2758)
Weld project now uses unified and automatic formatting and import sorting that happens during build (WELD-2753)

As always, if you find further issues with Weld 5, let us know and we’ll try to help.

[ Download ] [ Documentation ] [ Release notes ]

Weld 5.1.1.SP2

2023-8-9 release Matej Novotny

Another bug-smashing release has landed in Maven Central and this time it’s Weld 5.1.1.SP2.

This is a very small but important change which addresses possible memory leak scenario (WELD-2750). There are multiple conditions for this leak to occur and while most applications are unlikely to be affected, it is still recommended to upgrade to this latest version.

As always, if you find further issues with Weld 5, do let us know.

[ Download ] [ Documentation ] [ Release notes ]

Weld 5.1.1.SP1

2023-7-11 release Matej Novotny

A new SP release of Weld 5 is now avaiable.

Latest release, Weld 5.1.1.Final, has shown that one of the changes (WELD-2743) had unforseen and, sadly, untested consequences. Some of the integrators and some of community were using BeanManager#getReference in scenarios which were broken by this change. While the use cases aren’t explicitly backed by the specification or its TCKs, we decided we don’t want to break them, especially not in a micro release.

This SP release therefore aims to correct the above and only adds one other tiny change:

Revert the change of BeanManager#getReference and solve this issue differently (WELD-2745)
Modify how toString() is invoked on proxies of removed EJB beans (WELD-2747 )

Big thanks for (Laird Nelson) and (Arjan Tijms) for bringing these cases to my attention as well as helping to understand and resolve them!

As always, if you find further issues with Weld 5, do let us know.

[ Download ] [ Documentation ] [ Release notes ]

Weld 5.1.1.Final

2023-6-12 release Matej Novotny

It’s time for some minor updates and fixes, Weld 5.1.1.Final is now available!

Main highlights are as follows:

Fix bean type assignability for beans with recursive generic types (WELD-2738)
Failing validation for pasivation capability, Weld should throw DeploymentException instead of DefinitionException (WELD-2741)
Avoid firing ProcessInjectionTarget multiple times if a specialized bean was vetoed (WELD-2742)
BeanManager#getReference should not create a child CreationalContext instance (WELD-2743)
- This should only affect scenarios in which beans were 'manually' created and destroyed in which case the destruction could end up incomplete
Fix how Weld defines proxies to avoid problems in JDK 17+ along with the newest JBoss Class File Writer (1.3.0.Final) (WELD-2744)
Correction to documentation which incorrectly suggested @ManagedBean was a bean defining annotation (WELD-2737)

As always, if you find further issues with Weld 5, let us know and we’ll try to help.

[ Download ] [ Documentation ] [ Release notes ]

Weld 5.1.0.Final

2022-10-3 release Matej Novotny

Weld Core 5.1.0.Final and Weld API 5.0.SP3 are now availabe in Maven Central.

Most notable change, which is also the cause of a minor version bump, is the removal of Weld Probe from our codebase. Details are in this JIRA issue and were also communicated via weld-dev email.

In short, Probe hasn’t been maintained for a long time and its UI part is using outdated libraries and would need to be completely re-written which is something that we opted not to do at the moment. The JIRA issue has more information as to how we could re-integrate it in the future if there is interest from the community.

Warning

Probe removal affects any integrators that were using Probe up until now! This typically concerns EE integrators such as WildFly or Liberty.

As usual, here is a list of notable bugfixes in this version:

Made decorators more Groovy friendly (WELD-2713)
Updated Jandex and remove deprecated usages (WELD-2724)
Added tools to execute TCK lang model in EE container (using WildFly) (WELD-2725)
Introduced method to WeldManager which allows to obtain instances of all registered contexts regardless of whether they are active (WELD-2726)
Brought WildFly Arquillian dependency setup up to date and fix affected examples (WELD-2727)
AbstractResourceServices in Weld API now correctly take into consideration lookup value of @Resource (WELD-2728)
AbstractResourceServices now supports setter methods for @Resource where the name is defaulted (WELD-2732)
Corrected the implementation of WeldExpressionFactory#equals (WELD-2729)
Fixed BeanManager bean types to also include BeanContainer (WELD-2731)
Avoid logging information about non-bindings member when using BeanManager#isQualifier for annotations that aren’t qualifiers (WELD-2643)
Removal of Weld Probe (WELD-2733)

[ Download ] [ Documentation ] [ Release notes ]