Prepare for Quarkus 3.0.0

[turing85]

In the advent of the Quarkus 3.0.0 release, we should prepare this extension.

We depend on quarkus-artemis-jms, therefore we need builds of this extension in order to test compatibility.

Current release of quarkus-artemis-jms:

[turing85]

Necessary import changes:

• javax.enterprise -> jakarta.enterprise
• javax.inject -> jakarta.inject
• javax.transaction.TransactionManager -> jakarta.transaction.TransactionManager
  • curiously enough, javax.transaction.xa.XAResource was not moved to jakarta

[turing85]

It seems that the narayana version pulled in by quarkus (org.jboss.narayana.jta:narayana-jta-jakarta:jar:5.13.1.Alpha1) has not or not yet fully made the transition to jakartaee:

[ERROR] /eXchange/git/quarkiverse/quarkus-pooled-jms/runtime/src/main/java/io/quarkiverse/messaginghub/pooled/jms/PooledJmsWrapper.java:[48,28] cannot access javax.transaction.TransactionManager
  class file for javax.transaction.TransactionManager not found
[ERROR] /eXchange/git/quarkiverse/quarkus-pooled-jms/runtime/src/main/java/io/quarkiverse/messaginghub/pooled/jms/PooledJmsWrapper.java:[54,58] cannot access jakarta.jms.XAConnectionFactory
  class file for jakarta.jms.XAConnectionFactory not found

Line 47/48:

        JmsPoolXAConnectionFactory xaConnectionFactory = new JmsPoolXAConnectionFactory();
        xaConnectionFactory.setTransactionManager(transactionManager);

Line 54:

            JmsXAResourceRecoveryHelper recoveryHelper = new JmsXAResourceRecoveryHelper(xaConnectionFactory);

[turing85]

So this is a curious one. If we use pooled-jms version 2.0.5, we get the above error. If we use pooled-jms version 3.0.0, we have a version incompatibility in jarkarta.jms-api, since quarkus (and quarkus-artemis-jms) uses version 2.0.3, while org.messaginghub:pooled-jms uses version 3.0.0.

[turing85]

The version incompatibility is coming from quarkus-artemis-jms. The artemis jms client used pulls in jarkarta.jms-api in version 2.0.3.

[zhfeng]

javax.transaction.TransactionManager -> jakarta.transaction.TransactionManager

• curiously enough, javax.transaction.xa.XAResource was not moved to jakarta

I think it is because this package is provided by Java SE. see Jakarta Transaction spec

[zhfeng]

https://jakarta.ee/specifications/messaging/

• Messaging 2.0 for Jakarta EE 8
• Messaging 3.0 for Jakarta EE 9
• Messaging 3.1 for Jakarta EE 10

And from quarkus-dev Road to Quakrus 3, it will move to Jakarka EE 10. @maxandersen is it right?

[turing85]

With release 3.0.0.Alpha3 of io.quarkiverse.artemis:quarkus-artemis-jms and version 3.0.0 of org.messaginghub:pooled-jms, everything seems to work fine. We have to modify the configuration of the integration tests to enable the default configuration (adding quarkus.artemis.enabled=true to application.properties).

[turing85]

@zhfeng do you want to provide a branch for the migration? Or should I create a branch in my fork, and we transfer it later?

[zhfeng]

Thanks a lot @turing85 ! Please hold a branch in your fork. I willl creat a branch fro migration later. I still have some works on wrapping ConnectionFactory more generically and it might get rid of dependency on quarkus-artemis-jms.

[turing85]

fork branch

[ppalaga]

What is the status of the migration? Is there any estimate when we could expect a release compatible with Quarkus 3?