---

Overview

JMS provides very basic functionality for interacting with a messaging middleware and its missing lots of common functionality. Hermes includes the ability to have a plugin that interacts with middleware using the native API. This allows us to efficiently find out the depth of a queue for example without having to browse it, essential for the queue watching that Hermes does.

You configure the plugin in the sessions property configuration, its not current automatically detected.

Plugins oftem require additional configuration not available on the ConnectionFactory as the above example shows for WebLogic. Check the provider notes to see if there is a plugin for your JMS provider.

Implementation

When a plugin is used it takes the configuration from the JMS ConnectionFactory wherever possible. It does not try and cast into the providers internals rather it will create a new native connection. Each plugin implements a HermesAdminFactory that creates sessions that implements HermesAdmin. Within Hermes this session is closed as soon as possible after create - they do not linger when you're not doing anything with the GUI. To get an idea of how the plugins work, they exist in the hermes.ext package.