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 2281F1894A for ; Thu, 21 May 2015 21:28:18 +0000 (UTC) Received: (qmail 81969 invoked by uid 500); 21 May 2015 21:28:18 -0000 Delivered-To: apmail-cxf-issues-archive@cxf.apache.org Received: (qmail 81936 invoked by uid 500); 21 May 2015 21:28:18 -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 81821 invoked by uid 99); 21 May 2015 21:28:17 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 May 2015 21:28:17 +0000 Date: Thu, 21 May 2015 21:28:17 +0000 (UTC) From: "Andrei Shakirin (JIRA)" To: issues@cxf.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (CXF-6419) Update JMSEndpoint properties using EndpointInfo MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CXF-6419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrei Shakirin updated CXF-6419: --------------------------------- Description: There are some use cases, where client (or service) needs explicit control on some JMSEndpoint properties (for example durableSubscriptionClientId, durableSubscriptionName) not through the JMS URL, but using jax-ws properties. The reason: URL is often shared between client and service, but they must have different durableSubscriptionClientId for durable subscription. Currently only EndpointInfo Binding properties are checked. I would apply both EndpointInfo properties and Binding properties having special prefix: "jms.". That prevents potential conflicts with other jax-ws properties and opens the door to explicitly configure JMSEndpoint. was: There are some use cases, where client (or service) needs explicit control on some JMSEndpoint properties (for example durableSubscriptionClientId, durableSubscriptionName) not through the JMS URL, but using jax-ws properties. The reasone: URL is often shared between client and service, but they must have different durableSubscriptionClientId for durable subscription. Currently only EndpointInfo Binding properties are checked. I would apply both EndpointInfo properties and Binding properties having special prefix: "jms.". That prevents potential conflicts with other jax-ws properties and opens the door to explicitly configure JMSEndpoint. > Update JMSEndpoint properties using EndpointInfo > ------------------------------------------------ > > Key: CXF-6419 > URL: https://issues.apache.org/jira/browse/CXF-6419 > Project: CXF > Issue Type: Improvement > Components: JMS > Affects Versions: 3.1.0 > Reporter: Andrei Shakirin > Assignee: Andrei Shakirin > > There are some use cases, where client (or service) needs explicit control on some JMSEndpoint properties (for example durableSubscriptionClientId, durableSubscriptionName) not through the JMS URL, but using jax-ws properties. The reason: URL is often shared between client and service, but they must have different durableSubscriptionClientId for durable subscription. > Currently only EndpointInfo Binding properties are checked. I would apply both EndpointInfo properties and Binding properties having special prefix: "jms.". That prevents potential conflicts with other jax-ws properties and opens the door to explicitly configure JMSEndpoint. -- This message was sent by Atlassian JIRA (v6.3.4#6332)