JMS: Add support for jakarta.jms.ConnectionFactory

[matzalew]

Hello Gatling team :)

We would like to be able to use jakarta.jms.ConnectionFactory as the JMS, as it's the valid library for newer versions of Springboot.
Currently it is not available.

[slandelle]

Are you interested in contributing or sponsoring this feature (note: we can’t drop javax support either)?

[slandelle]

Also, I'm a bit puzzled here. Unless I'm mistaken, the actual ConnectionFactory class you need is the one supported by your actual JMS client library (IBM MQS and friends). Springboot might be providing adapters, but still, unless you're using an updated client, you still have the old javax classes in your classpath.
And I really wonder how many JMS users have upgraded their JMS broker to move to the new "Jakarta EE" stack.

We'll most likely do this move someday, but when there will be enough demand for it.
As of today, you're the only OSS user to request it, and none of our Enterprise customers did.

[slandelle]

@matzalew any update regarding the first part of my message? Were you able to find a workaround and use the "old" package?

[matzalew]

Sorry, missed your messages.

Did not found workaround.

I could try to contribute. But never done such thing, and I got likely limited time after my working hours. So no promises - but I'd like at least to try.

[holomekc]

Hmm not sure how to tackle this. The only idea I have is to basically duplicate everything, and change the import when necessary, and use a different package:

[holomekc]

Normally other libraries create two releases. One with javax and one with jakarta. This makes the duplication unnecessary. e.g.
gatling:3.10.4
gatling:3.10.4-jakarta

although I would like the other way around more:
gatling:3.10.4-javax
gatling:3.10.4