Subject summarizes my question: I can not seem to find an RAR artifact that is 'ok' for a remote AMQ broker 5.17x/5.18x but is suitable for Jakarta based application platforms like Wildfly 26x and greater.
Does one exist? (Or is there a recipe to provide a workable solution?) This GAV: 'org.apache.activemq:activemq-client-jakarta:5.18.6' is OK for Jakarta based clients just pushing messages (using AMQ jakarta client APIs more directly). Doesn't help for listeners/mdbs. Constraints: Need to migrate dozens of MDB based on JavaEE & JMS 1.0/1.1 (currently running on Wildfly and older JBOSSes) to newer JakartaEE on Wildfly > 26 (34.x or greater). All use a remote AMQ classic broker. All MBDs use JMS 1.0/1.1 level JavaEE API -- Will NOT try to use new Jakarta JMS style features & APIs beyond compatibility with older JMS 1/1.1 specs. Moving to Artimis broker is not an option. Moving to AMQ Classic 6.x broker is not an option in the same time frame as I need to migrate to newer Wildfly servers. YES: the AMQ 6.1.x RAR in a Wildfly > 26.x does seem to work OK against a 5.17.x/5.18.x remote broker -- minimal bench testing only. I feel it is in better form to keep the client side (rar or jar) as close as possible to it's broker and probably 'less desirable' to use newer major client side (rar or jar) to connect to an older broker. Correct?
