This is a question/poll targeted at the current and future users of the Axon CDI extension.
The current implementation of the CDI extension has Alpha status, and works reasonably well with Axon 3.3.x and 4.0.x.
In my own time I have begun a rework of the extension’s internals that hopefully will pull it out of Alpha status, and targets Axon 4.x,
probably starting at 4.2-SNAPSHOT since that is the current Axon “master”. My goal is to more closely parallel the
services provided by the Spring module. For unit testing I am using Weld-SE, so no need for Arquillian or Cargo.
The current Axon CDI extension targets CDI spec 1.1 by including a “provided” dependency on Java EE 7. The current
version, included in Java/Jakarta EE 8 as well as Eclipse MicroProfile is CDI 2.0. This is also supported by Weld-SE,
although that should not be surprising as it’s the reference implementation for the spec.
I would like to get a general feeling for the need to stick to CDI 1.1, as it requires quite a bit of boilerplate code to
wrap Beans, or the inclusion of an additional dependency on something like Apache DeltaSpike.