Return-Path: X-Original-To: apmail-cxf-issues-archive@www.apache.org Delivered-To: apmail-cxf-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B493E11FAD for ; Mon, 2 Jun 2014 13:57:02 +0000 (UTC) Received: (qmail 67929 invoked by uid 500); 2 Jun 2014 13:57:02 -0000 Delivered-To: apmail-cxf-issues-archive@cxf.apache.org Received: (qmail 67825 invoked by uid 500); 2 Jun 2014 13:57:02 -0000 Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cxf.apache.org Delivered-To: mailing list issues@cxf.apache.org Received: (qmail 67701 invoked by uid 99); 2 Jun 2014 13:57:02 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Jun 2014 13:57:02 +0000 Date: Mon, 2 Jun 2014 13:57:02 +0000 (UTC) From: "Andrei Shakirin (JIRA)" To: issues@cxf.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (CXF-5780) JMS pubsub: support different parameters for clientID and durableSubscriptionName MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 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)