JMSTransportListener doesn't allow for predefined JMS ClientId

Issue #31 resolved
Anonymous created an issue

Spring allows you to set the JMS ClientID on the connectionFactory and in fact for durable subscribers, this is necessary as the setting the clientID must be the first operation.

The JMSTranportListener doesn't have an option to bypass setting the clientID - it must be either set specifically in the properties or else it takes on the name of the listener.

Specifically with durable subscribers, this will cause an error. I'm no export but I would imagine that if the listener property subscriptionDurable=true then the clientId should be ignored at this stage and a warning given if the admin also attempts to set the clientId on the listener.