You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cxf.apache.org by GitBox <gi...@apache.org> on 2022/03/14 20:26:43 UTC

[GitHub] [cxf] jbertram commented on pull request #919: Switching to ActiveMQ Artemis

jbertram commented on pull request #919:
URL: https://github.com/apache/cxf/pull/919#issuecomment-1067254805


   Hey folks. I'm on the ActiveMQ PMC and I can confirm what @jimma has said. The goal of the ActiveMQ community is to make Artemis the next major version of ActiveMQ (i.e. 6.0). 
   
   I'm not clear on the entire use-case here, but if you're embedding ActiveMQ and using it internally then it should be a pretty straight-forward migration assuming you aren't making use of many ActiveMQ-specific features. Looking through @reta's PR it looks pretty much as I would expect.
   
   For what it's worth I'm looking at helping TomEE support ActiveMQ Artemis right now based on a recent [discussion like this](https://lists.apache.org/list?dev@activemq.apache.org:lte=1M:Jakarta%20compatible%20version%20of%20ActiveMQ%20classic) on the ActiveMQ dev list, although I've been covered up with other work recently.
   
   I think the sooner projects like CXF, TomEE, etc. migrate the better position we'll _all_ be in. At the very least it will reduce pressure on ActiveMQ to duplicate work on the "Classic" broker that's already been done on Artemis.
   
   I'm willing to answer any questions anybody has, technical or otherwise, about CXF's potential migration to Artemis. I would volunteer to help with the coding, but @reta seems to have that in hand already.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@cxf.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org