Weld 6.0.0.Alpha1

2023-10-26   release   Matej Novotny

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 CDI API design and PR, take a look (here)

    • Note that this feature is still being improved on both, CDI side and (Weld side) but the general shape of it is already carved out

  • Support standardized means of getting interceptor bindings from InvocationContext (WELD-2756)

    • This was already possible via set of methods in WeldInvocationContext as well as the String key under which we stored these bindings in InvocationContext

    • Both of the above are no deprecated (but still working) and users are expected to use the standardized approach

  • Support inspectable CreationalContext and Contextual in CDI TCK SPI (WELD-2757)

Other bugfixes and project QoL features:

  • Fix proxy creation for beans using @Typed and having package-protected types split across packages (WELD-2758)

  • 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)

  • WeldManager#getContexts now correctly returns an empty set when there are no contexts for given scope (WELD-2761)

  • Fix possible memory leak with repetitive thread group creation (WELD-2755)

  • WeldInitialListener can no longer throw NPE is application fails to start (WELD-2752)

    • Only possible in some EE containers on repeated re-deployment of Weld applications

  • LazySessionBeanStore no longer swallows exceptions happening when attempting to initiate HTTP session (WELD-2762)

  • Weld Core and Weld API are now using formatter plugin and impsort instead of checkstyle (WELD-2753)

  • Jandex version was bumped to 3.x across the project (WELD-2754)

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

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.

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.

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.

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.