Question regarding Errai Roadmap / CDI 1.1

[jtysper]

Hello everybody,

I have a question regarding the Errai Roadmap.

For Errai 3.1 it already marks "Upgrade to Weld 2 / CDI 1.1 (minimum requirement)" as "DONE".

I am a little bit worried about the "minimum requirement" part.

We are operating an WebSphere Application Server and as of now IBM didn't even announce a Java EE 7 compatible version of their product.

Does this mean that we won't be able to upgrade to Errai 3.1 for the next months/years?

We just recently got the Weld dependency out of Errai 2.3 and 3.X and can now use the framework as it was originally intended (we had to use an ugly "Errai @Service" => CDI bridge until now and couldn't use distributed CDI Events).

It would be really unattractive to have to reintroduce these kinds of hacks again or stay with Errai 3.1 from now.

Could you please reveal the impact of this new CDI-1.1 requirement?

Does it only apply to specific "advanced modules" of Errai or is the core bus itself affected?

Kind Regards

Jörn

[csa]

Hi Jörn,

You can find all the details about this issue here: https://issues.jboss.org/browse/ERRAI-700

We had to upgrade to CDI 1.1 as there was no other option for us going forward.

However, it will be possible for you to upgrade all other Errai modules to 3.1.x and keep using our CDI integration module (errai-weld-integration.jar) in version 3.0.x. So, you should be able to use new Errai functionality and still deploy to old (CDI 1.0) containers.

Cheers,

Christian

[jtysper]

Ah, ok.

Thanks!

Is it possible to freeze the 3.0.x version of errai-weld-integration as errai-cdi-1-0 or sth for 3.1.x etc builds?

Would make me feel much safer since it won't be that easily forgotten that there are still people out there relying on pre-jee7 containers ;-)

Regards

Jörn