WunderBoss messaging bindings for ActiveMQ Artemis
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.



This allows WunderBoss-based systems (Immutant, TorqueBox) to use ActiveMQ Artemis instead of HornetQ for messaging.

What is Artemis?

Artemis is the next generation of ActiveMQ, and is based on a merging of the ActiveMQ and HornetQ code bases.


In theory, you should be able to exclude org.projectodd.wunderboss/wunderboss-messaging-hornetq from your dependencies, and depend directly on org.projectodd.wunderboss/wunderboss-artemis. In reality, it may be a tetch more complicated.

With Immutant

First, you'll need to depend on Immutant 2.1.0 or newer, then make a few adjustments to your :dependencies:

:dependencies [[org.immutant/messaging "2.1.3"
                :exclusions [org.projectodd.wunderboss/wunderboss-messaging-hornetq]]
               [org.projectodd.wunderboss/wunderboss-artemis "0.2.0"]]

Note that this will only currently work outside of WildFly, since Artemis is not yet available in the container, and this project doesn't yet provide the proper bindings to access it even if it was available.

With TorqueBox

TBD - it will likely require a gem, since the wunderboss-messaging-hornetq is embedded within the torquebox-messaging gem.

Overriding the default configuration

If you need to customize the configuration, you just need to provide a broker.xml on the classpath. You can use our default one as a base, and refer to the Artemis docs for help.


wunderboss-artemis is licensed under the Apache License, v2. See LICENSE for details.