Andrei Shakirin created CXF-5780:
------------------------------------
Summary: JMS pubsub: support different parameters for clientID and
durableSubscriptionName
Key: CXF-5780
URL: https://issues.apache.org/jira/browse/CXF-5780
Project: CXF
Issue Type: Improvement
Reporter: Andrei Shakirin
Assignee: Andrei Shakirin
Currently the DurableSubscriptionName endpoint parameter is used also as
connection clientId in JMSFactory.
There are use cases where these two parameters should be configured separately
(for example if two different clients use the same subscription name for the
topic).
I would propose to introduce additional endpoint parameter for clientID
--
This message was sent by Atlassian JIRA
(v6.2#6252)