Improve JMS integration

[cescoffier]

Description

• How should we support JMS?

1. Raw JMS API usage
2. Message-Driven-bean support
3. Reactive Messaging connector

• How do we handle transactions and the myriads of JMS servers?
• What's missing with our current approach (low-level)?

Analysis

(links to analysis docs containing architecture design work, requirements gathering, etc)

[quarkus-bot]

/cc @ozangunalp (reactive-messaging)

[Serkan80]

My opinion would be to go with the reactive-jms approach. The current JMS approach looks bloated and complicated. It’s even more complicated than the old school MessageDriven way.

[mexavier]

Hi @cescoffier

I needed to connect to an existing ActiveMQ servers.
For this usage, we activated AMQP protocol on ActiveMQ and began to use smallrye-messaging-amqp that is easy to use and elegant.

However we had issue to support loadbalancing as the ActiveMQ servers were in cluster and to manage server disconnections.
For that, we used qpid-jms that works well but it is harder to used.

For me, improving smallrye-messaging would be great.

[cescoffier]

@mexavier We have a JMS connector - however it's not currently supported in Quarkus (it's usable in JVM mode).