ARTEMIS-3164:Support prefix to create temporary resources.

[anmol-saxena-14]

Add two new acceptor URL parameters — temporaryQueuePrefix and temporaryTopicPrefix — that allow brokers to recognise destination prefixes as signals to create temporary resources.

When a STOMP client subscribes to a destination matching a configured temporary prefix, the broker:

• Strips the prefix to derive the bare address/queue name.
• Creates a temporary ANYCAST queue (for temporaryQueuePrefix) or a temporary MULTICAST queue (for temporaryTopicPrefix).
• Registers the resource for automatic deletion when the client connection closes.

This mirrors the hard-coded /temp-queue/ and /temp-topic/ behaviour of ActiveMQ 5.x, easing migration of STOMP clients to Artemis.

[jbertram]

The names of the parameters here should mimic anycastPrefix and multicastPrefix. You're currently using temporaryQueuePrefix and temporaryTopicPrefix. Instead you should use temporaryAnycastPrefix and temporaryMulticastPrefix or possibly shorten it to tempAnycastPrefix and tempMulticastPrefix.

[jbertram]

This is a nitpick, but your commit message format should be something like <JIRA> <shortMessage> with no punctuation, e.g.:

ARTEMIS-3164 support prefix to create temporary resources

[anmol-saxena-14]

This is a nitpick, but your commit message format should be something like <JIRA> <shortMessage> with no punctuation, e.g.:

ARTEMIS-3164 support prefix to create temporary resources

Thanks for pointing this out. Going forward, I’ll follow this practice.

[anmol-saxena-14]

Renamed the two new acceptor URL parameters introduced for temporary resource support to align with the existing anycastPrefix and multicastPrefix naming convention:

  > temporaryQueuePrefix  -> temporaryAnycastPrefix
  > temporaryTopicPrefix  -> temporaryMulticastPrefix