HornetQ to Artemis migration

[c0c0n3]

HornetQ was donated to Artemis, so we have to migrate to Artemis. Also, the SpingBoot HornetQ starter reached end of life in the 1.4.x series and is not available for 1.5.x.

Purely from a code migration standpoint, It doesn't look like this is a train smash for us. In fact,

• Artemis still has the same classes of the HornetQ core API we've used, only in a different namespace
• SpringBoot should work exactly the same according to the 1.3.4 docs

But is the HornetQ core functionality we've used still the same in Artemis? Only time and lots of testing will tell...

[c0c0n3]

Docs need an upgrade too! (Warning: donkey work ahead...)

Here's the list of docs site sections to update:

• Configuration / Security / File System
• Design / Tech Stack
• High-level View / Conceptual Overview (including diagram)
• High-level View / Codebase Essentials (including diagram)
• Messaging (including diagrams: key-q-classes.svg, omero-import-gc-wiring.svg, omero-import-wiring.svg)
• Process View / Processes & Threads
• Process View / Distribution

And for the JavaDoc, all the HornetQ classes in:

• ome.smuggler.config
• ome.smuggler.providers.q

[c0c0n3]

Dead letter/expire address warnings

Artemis logs warning messages at start up for each and every queue that has no associated dead letter/expiry address. (See this issue.) We're not using dead letters and expiry addresses at the moment cos we have our own failure handling mechanism built into the messaging API. Couldn't find an easy way to tell Artemis to suppress those warnings, so for the time being we'll have to live with them.

[c0c0n3]

implemented changes in v1.1.0-beta, see #11.