> protocol interoperability is available but still It looks like code
changes are required from the client side.
What code changes are required for OpenWire clients to connect to Artemis?
Please be as specific as possible.
> Will clients using ActiveMQ client jar be able to connect to the broker
Regarding interoperability: As you mentioned protocol interoperability is
available but still It looks like code changes are required from the client
side.
To be more specific : Will clients using ActiveMQ client jar be able to
connect to the broker running with Artemis ?
Eg: Currently clients
Artemis supports all the same clients plus an extra one. It supports the
Core protocol (The Artemis native protocol), OpenWire(which is the ActiveMQ
5.x native protocol), AMQP, MQTT, and STOMP. So any of your existing
clients will work with the broker as long as you have enabled the protocol
supp
How hard would be to switch just the messaging server from ActiveMQ to
Artemis. There are a lot of JMS, Perl, Python clients connecting to our
ActiveMQ instance.
Is Artemis being developed as drop-in replacement for ActiveMQ that can work
seamlessly with activemq-client libraries without much chan
Artemis is intended to be the follow on to ActiveMQ 5.x. It is currently
being actively developed to add new features to it with the goal that the
useful features from ActiveMQ will also be added to Artemis. Most of the
development effort is being done there and ActiveMQ 5.x is basically in
maint
What is the difference between Artemis and current ActiveMQ versions? When
should one be preferred over another? Is there any difference between
features?
Artemis docs say it has outstanding performance - should this be preferred
over ActiveMQ? How stable Artemis is in production environments?
I h
