This project provides Spring Integration extensions for inbound and outbound channel adapters.
Configuring a Client Factory
Both the inbound and outbound adapters require a client factory which is responsible for creating an instance of an io.iron.ironmq.Client. This project provides a default implementation of the factory and a namespace handler.
The example below shows the creation of a default client factory using SpEL to get the IronMQ projectId and token values.
Configuring the Inbound Channel Adapter
Shown below is an example of an inbound channel adapter configuration. I will skip the requisite beans root element and default-client-factory element as it is shown above in the docs. The inbound queue can be defined either as a regular literal/SpEL at initialization or a SpEL expression evaluated each time receive() is called on the underlying MessageSource.
Configuring the Outbound Channel Adapter
Shown below is an example of an outbound channel adapter configuration. As above, I will skip the requisite beans root element. The queue-name value is a literal value below, but you can use expressions as well that will be evaluated each time receive() is called on the underlying MessageSource.
Caveats
The Iron MQ Java libraries used in this project were authored by @iron-io but they're not yet available on a central maven repository. You will need to install them into your local repository. You can install the file (currently checked in to this project under repo/... yeah, i know) via the following command:
Support or Contact
Submit any issues on the GitHub issues page. I'll do my best to address any issues quickly.