News

Weld 6.0.3.Final

2025-5-20   release   Matej Novotny

Weld 6.0.3.Final release is now available in Maven Central.

There are only two fixes to mention here:

  • Added validation for interceptor classes declaring multiple methods for the same interception type (WELD-2814)

    • This is a fail-fast(er) mechanism for users; otherwise the behavior is mandated by the Interceptors specification

  • Correct AnnotatedType ID creation to avoid cache miss leading to possible memory leak (WELD-2815)

    • The leak is not generic and doesn’t affect most deployments. In fact it requires at least all of the below condition to start appearing:

      • Using CDI producers along with InterceptionFactory

      • Repeatedly creating these beans, so most likely @Dependent bean

      • And most importantly, the AnnotatedType backing the bean has to have an annotation with a non-empty array type value

    • Even if this issue is unlikely to manifest, we recommend users to update their Weld version if possible

If you find any issues with the current release, don’t hesistate to report them via usual channels.

[ Download ] [ Documentation ] [ Release notes ]

Weld 5.1.6.Final

2025-5-20   release   Matej Novotny

Weld 5.1.6.Final is now headed towards Maven Central with a tiny fix for potential memory leak.

There was a very specific scenario possibly leading to a memory leak due to caching mismatch.
Note that this only occured if the following conditions were met:

  • Having a producer using InterceptionFactory

  • Repeatedly creating those bean (most likely @Dependent beans)

  • The underlying AnnotatedType backing this bean had to have an annotation with a non-empty array type value

Because this requires a very narrow set of conditions, it is reasonable to believe that most deployments are unaffected.
That said, if you can upgrade, we definitely encourage you to!

For more details and links to the PRs, feel free to browse WELD-2815 JIRA.

[ Download ] [ Documentation ] [ Release notes ]

Moving to a Foundation

2025-5-7   team   Matej Novotny

Just like other projects in the ecosystem around us (WildFly, SmallRye, RESTEasy, Undertow, …​), Weld too has been looking for a friendly vendor-neutral place it could inhabit - a software foundation.
It is our hope that by joining a foundation we can make Weld more open, expand the community, improve transparency and encourage participation from contributors coming from all over the software landscape.

Things to Keep in Mind

When choosing a foundation to join, there are several importants things to consider:

  • Ability to use the tooling we currently have to minimize the impact of the move. For instance, we still use JIRA for issues.

  • Maintain the ability to perform quick release when needed and at flexible intervals.

  • As a project, retain independence in decision-making. I.e. if possible do not fall under foundation imposed restrictions and rules.

What Does the Move Entail?

Red Hat has always been supportive of open source and collaboration in vendor-neutral projects and this is still the case; Red Hat bussiness leaders are fully supportive of this move.
Furthermore, we, as in the Weld team, aim to keep working on the project and supporting it just like we did up until now.

Current Status

At the moment we are eyeing the option to move along with WildFly under the Commonhaus Foundation.

Community Feedback

We’d love to hear your thoughts on this so don’t hesitate to speak through the mailing list or via a discussion topic directly in the GitHub repository.

Best Regards
Matej

Weld 6.0.2.Final

2025-4-3   release   Matej Novotny

Here we are with yet another small update to Weld 6; say hello to Weld 6.0.2.Final.

Changes in this version:

  • Support for records in the CDI Lang Model (WELD-2809)

  • Container lifecycle observers can now inject any subclass of BeanContainer into them (WELD-2811)

  • Substantially improved exception messages for invokers (WELD-2812)

As always, do report any bugs you encounter so that we can squash them as soon as possible!

[ Download ] [ Documentation ] [ Release notes ]

Red Hat Middleware Strategy

2025-3-27   team   Matej Novotny

By now you might have heard that Red Hat announced significant changes to their middleware strategy last month.
Let me start by saying that this has come as a surprise to us as we were not aware of it in advance.
Nonetheless, here we are, and I wanted to provide Weld community with some context as well as talk about how this affects the project.

If you want to read the official announcement, it can be found on the Red Hat blog.
In short, some key points from the article are:

  • Red Hat’s Middleware and Integration Engineering and Products teams are moving to IBM in May/June 2025.

  • Red Hat will continue to sell and support its Middleware and Integration offerings as they do today; this will not be impacted.

  • All transitioning Red Hat technology will remain open source and continue to follow an upstream-first development model.

I do not anticipate this change having any significant impact on Weld project perhaps with the exception of a temporary disruption during the transition period.
We remain committed to development of Weld as the compatible implementation of Jakarta CDI specification as well as its standalone capabilities.
The project remains open source and contributions as well as bug reports are still very much welcome!

For Weld team
Matej

1 2 ...20 21 Next