JMS connector implementation

[neeleym]

Hi ,
This is a repeat post from over at the Zulip Kogito group, but it may be directly related to the smallrye-jms implementation. I'm not sure.
I have been attempting to use this guide ( https://blog.kie.org/2021/09/kogito-process-eventing-add-ons.html ) to pass Process Events to ActiveMQ 5 via JMS. The guide, of course, uses Kafka as a connector to the outside. I am changing out the MP parms in the application.properties file to instead use "smallrye-jms". It doesn't seem to like this as a connector in that I continually get the following two lines in the build:

2022-07-27 15:57:09,607 WARN [io.qua.arc.pro.BeanArchives] (build-1) Failed to index org.eclipse.microprofile.reactive.streams.operators.PublisherBuilder: Class does not exist in ClassLoader QuarkusClassLoader:Deployment Class Loader: TEST@5906ebfb 2022-07-27 15:57:09,610 INFO [io.qua.arc.pro.IndexClassLookupUtils] (build-1) Class for name: org.eclipse.microprofile.reactive.streams.operators.PublisherBuilder was not found in Jandex index. Please ensure the class is part of the index.

This ultimately ends in a test failure. My main question is: Am I attempting to use a combination of messaging configurations that are not ready to be used in this manner? or will not be made available for microprofile use ever ( e.g. smallrye-jms )? Is there a better alternative for a connector that will allow me to publish Process Events to ActiveMQ 5 via JMS that I should be using?

Using:
Kogito 1.23
Quarkus: 2.10.3

[cescoffier]

The JMS connector is not supported in Quarkus. So, I don't believe it would work OOTB (actually, your report indicates that it does not).