Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Branch: master
Pull request Compare This branch is 19 commits behind jbrisbin:master.

Fetching latest commit…

Cannot retrieve the latest commit at this time

Failed to load latest commit information.
bin
src
.gitignore
LICENSE
README.markdown
pom.xml

README.markdown

Installing

Download the latest binary package:

http://github.com/jbrisbin/rabbitmq-dsl/downloads

Unzip in your desired location:

cd /opt
sudo tar -zxvf ~/rabbitmq-dsl-1.0.x.tar.gz

Get the list of possible command-line switches:

cd rabbitmq-dsl-1.0.x
bin/mqdsl -?

Building

Clone the source code:

git clone git://github.com/jbrisbin/rabbitmq-dsl.git

Build a jar file of the command-line DSL runner:

cd rabbitmq-dsl
mvn -Dmaven.test.skip=true package

Copy the dependencies into a directory called "lib":

mkdir lib
mvn dependency:copy-dependencies -DoutputDirectory=lib

Then create a directory for your log files (or edit the bash script to put log files elsewhere):

mkdir log

These directories are not tracked in Git, so you have to keep them updated manually (if anyone wants to contribute a patch to do this automagically, it would be appreciated! :).

To use the DSL runner, execute the bash script located in "./bin":

bin/mqdsl -?

...will give you a run-down on what options are available.

Note on login information:

If you create a file in your home directory called ".rabbitmqrc" and place the following properties inside it, you don't have to specify them on the command line:

vi ~/.rabbitmqrc
...
mq.host = rabbitmqserver.mycompany.com
mq.port = 5672
mq.user = mquser
mq.password = mqpass
mq.virtualhost = /

Notes:

  • There is a unit test that will run in the normal Maven build stage. Look in the src/test/groovy/rabbitmq-test.g file to see the full text of the DSL test. To run the test, you'll need to specify the property "log.dir" (in the bash script, defaults to "./log").

RabbitMQ Groovy DSL

The Groovy DSL (Domain Specific Language) for RabbitMQ allows you to mix standard Groovy code with a builder-style syntax for working with a RabbitMQ server. For example, consider the following:

mq.exchange(name: "test", durable: false, autoDelete: true) {
  // Named, non-durable queue
  queue name: "test", routingKey: "test.key", {
    consume tag: "test", onmessage: {msg ->
      log.info(msg.bodyAsString)
    }
  }
}

This example uses the RabbitMQ DSL to:

  1. Declares a non-durable, autodelete exchange named "test"
  2. Declares a named, non-durable, autodelete queue named "test" and binds that queue to the enclosing exchange.
  3. Creates a queueing consumer (tagged with "test") that executes the "onmessage" closure every time a message is received.

Usage:

The Groovy DSL is intended to be used to create compact, self-documenting, RabbitMQ code similar to what ActiveMQ users have with Camel. Nesting queues within exchanges ensures that an exchange exists and that all queues are properly bound before your Groovy code is actually run.

If you want an anonymous, server-generated queue name, set the "name" property to "null":

mq.exchange(name: "test", durable: false, autoDelete: true) {
  // Anonymous, non-durable queue
  queue name: null, routingKey: "test.key", {
    consume tag: "test", onmessage: {msg ->
      log.info(msg.bodyAsString)
    }
  }
}

To publish messages, use the "publish" node:

 // Publish some messages
  queue routingKey: "test.key", {
    publish body: "this is a test"
  }

If you set the "body" property to a string, the builder will call .getBytes() on it and set the body of the message to that. If you set the "body" property to a real byte array (maybe you read in a file or posted a file, or something), it will blindly use what you give it. If you want to pass a closure, you can do that too:

  queue routingKey: "test.key", {
    publish myHeaderValue: "customHeader", body: {msg, out ->
      msg.properties.contentType = "text/plain"
      out.write("these are test bytes".bytes)
    }
  }

The "msg" variable passed to your closure is actually a lightweight bean wrapper that puts an instance of AMQP.BasicProperties ("properties"), an AMQP Envelope ("envelope"), and the body ("body" and "bodyAsString") onto a single object, which makes the bean introspection in Groovy happier.

If you want to run arbitrary Groovy code and access the RabbitMQ Channel object directly, declare a closure like so:

mq {channel ->
  // Do channel-specific stuff here...
  channel.exchangeDelete("test.exchange")
}

Notes:

  • Returning a non-null or "true" result from the closure specified on the "onmessage" property causes the consumer to keep listening for messages until the closure returns a false or <NULL> value.

License:

The RabbitMQ DSL is licensed under the Apache 2 license (included).

Something went wrong with that request. Please try again.