Thanks for that. That's a good point about the OpenWire protocol. The project I referenced in my previous message uses the Artemis client in TomEE adding the necessary jars. If using the ActiveMQ 5 client works with Artemis, then those changes might not be needed. I'll add the example in any case.
>From my point of view, being able to connect to both brokers makes sense. Jon On Wed, 9 Jan 2019, 16:08 exabrial12 <[email protected] wrote: > So a couple of notes from the field: > > * You can connect TomEE to an Artemis broker right now. Artemis can speak > the OpenWire protocol and the ActiveMQ Client in TomEE does too. :) > * Artemis has a dispatch and scalability advantage over ActiveMQ5. But, > only > if you are using an external broker. ActiveMQ5 with the vm://localhost > transport is stupendously fast. > * Even if you're using ActiveMQ5 as an external broker, you're not going to > notice a performance benefit from using Artemis externally until you have a > very large number of topics, queues, or messages (multiple thousands of > each) > > From a software engineering standpoint: > > * JMS2.0 support in TomEE is done with a shim over the legacy JMS Api. It > would be significant decrease in LOC to maintain if we could have native > support from the Artemis Client. > * I don't know if the Artemis client can connect to an external ActiveMQ5 > broker though. That would be sweet if it could > * I like the idea of supporting both brokers externally > > > > -- > Sent from: > http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html >
