Make destination ref and name properties consistent for JMS adapters [INT-920]

[spring-operator]

Mark Fisher opened INT-920 and commented

All adapters use attributes named "destination" when the actual reference is expected, and that is fine.

However, when expecting a name, some use a combination of "destination-name" and "pub-sub-domain" while others avoid the need for that boolean by using "queue-name" OR "topic-name". We should refactor such that ALL of the adapters use the mutually exclusive "queue-name" or "topic-name" attributes.

---

Affects: 2.0 M1

[spring-operator]

Mark Fisher commented

Moving to M4. Reconsidering this since it would be a breaking change.