Moving forward Narayana CDI spec dependencies to 2.0

[ochaloup]

Hi,

based on the changes coming from [JBTM-3106] Firing an @Initialized(TransactionScoped.class) event - JBoss Issue Tracker  I found the Narayana implements CDI spec in version 1.2 (

https://github.com/jbosstm/narayana/blob/5.9.5.Final/pom.xml#L455). I think it would be a good idea to move to 2.0.

From the user perspective there is some more events to be fired during transaction processing (e.g. @BeforeDestroy).

What do you think about this idea? tomjenkinson mmusgrov

Ondra

[tomjenkinson]

It looks feasible in the sense that when integrating with WildFly at least they appear to be 2.0: wildfly/pom.xml at 349dc917fedb6d6ef5a66eafb41584621fb3b583 · wildfly/wildfly · GitHub since [WFLY-10740] Update Weld to 3.0.5.Final (core and API) and CDI API to 2.0.SP1 - JBoss Issue Tracker

Does it have any backwards compatibility issues for Narayana? E.g. do we have to wait till version 6 of Narayana to do this?

[ochaloup]

The question about the need to propose the Narayana version 6 was another question which I have had in my mind.

The integration to WFLY should not make an issue. 2.0 is implemented for WFLY already for two years.

The compatibility issue is that the new release of jta-cdi of Narayana will need to be deployed to containers supporting 2.0. Otherwise there should not be an issue. If we will do so we need to check with containers, the Narayana is implemented at, if they support CDI 2.0.

With knowing this I'm not sure if we need to go with 6.0.0 with such change or we can go just with 5.10.

Ondra

[tomjenkinson]

If it means we could not deploy into a CDI 1.2 container any more I think we should go with Narayana 6