Is it preferred to specify the durable subscription name using the or as a activation-config property?
Is one way for backward compatibility? Which is preferred?
Also, is it possible to define a subscription to a topic at the MQ level rather than in a bean deployment descriptor? This doesn't seem to be an option.
The connection pool connector-resource takes a ClientId property, but lacks a corresponding way of entering the subscription name. Aren't both ClientID and SubscriptionName required?