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.

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)

Weld 5.0.1.Final

2022-6-24   release   Matej Novotny

Weld Core 5.0.1.Final is now available and comes with Weld API 5.0.SP2.

Main highlights are as follows:

  • Updated all CDI related versions (API and TCKs) to their latest released variants and made sure we are passing

  • Updated many other EE 10 APIs to their latest releases

  • We are once again fully continuously testing against an EE container (nightly WildFly builds) which helped us polish more bumps in tests and code

  • Tomcat 10.1 is available and supports EE 10, so we have upgraded to test against that and can therefore confirm our support for servlets is working well

  • Jetty support is at the moment not verified as there is no public Jetty 12 release to test against

  • Reviewed Servlet related parts of our documentation and updated them

  • Reviewed Weld SE-Servlet cooperation and renewed continuous testing for it

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

Weld 5.0.0.SP2

2022-6-8   release   Matej Novotny

Another quick turnaround as more integrators adopt Weld 5 and help us squash bugs. Weld 5.0.0.SP2 is headed into Central as we speak.

The main reason for this service release is WELD-2721 which was a spec violation in how AfterBeanDiscovery methods were treated outside of lifecycle observer method invocations. Apart from that, there was also a corner case NPE during Weld Servlet and SE cooperation bootstrap (WELD-2720).

As always, if there are more problems with Weld 5, let us know and we’ll try to help.

Weld 5.0.0.SP1

2022-5-4   release   Matej Novotny

A new version of Weld core is now in Maven Central - 5.0.0.SP1.

There have been reports of a bytecode verification error in certain scenarios reported by GlassFish and WildFly trying to integrate Weld 5.0.0.Final. We have investigated the cause and identified the problematic change, you can read more about it in WELD-2719.

Weld 5.0.0.SP1 release reverts the offending change (WELD-2712) and otherwise keeps Weld intant in terms of changes. In case you identify any further issues, don’t hesitate to reach out.

Weld 5.0.0.Final

2022-4-29   release   Matej Novotny

CDI 4 has passed its Final ballot and is now available in Maven Central. Some of you may have played with it already, but where is the fun in it, if you don’t have a Final implementation, right? Have no fear, Weld 5 Final is here!

As usual, there is Weld 5.0.Final API as well as Weld 5.0.0.Final core impl.

It is very much the same as CR2, with some additional tweaks and fixes that came to light when working on integrations within EE servers. That’s right, EE servers are already making progress towards integrating CDI 4 and Weld 5. Folks over at Open Liberty did their Weld 5 homework about a week ago and WildFly now has a pending pull request that adds missing bits for CDI 4 support. It might still be a while before there is a Beta WildFly release, but if you have the nerves, you can build the SNAPSHOT at least.

Back on the topic of changes, here is a list of fixes from CR2 to Final:

  • Self-interception can now be used on protected methods, params and return types (WELD-2712)

  • Rewieved Weld examples and made sure they run for EE 10 (WELD-2708)

  • Review Weld 5 documentation (WELD-2696)

    • Note that the servlet part is still outdated and being worked on as we need to see if there is workable EE 10 variant, see WELD-2716

    • We expect that this will be sorted by the time we ship 5.0.1.Final

  • Firing of the Startup event for web modules can happen too early (WELD-2717)

  • Synthetic beans coming from Build Compatible extension should be registered under their respective extensions (WELD-2718)

  • Exceptions thrown during execution of Build Compatible extensions now correctly preserve their cause (WELD-2710)

  • Some of our SE testing was being skipped ever since Groovy dependency update, this is now corrected (WELD-2714)