You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@cxf.apache.org by "Andrei Shakirin (JIRA)" <ji...@apache.org> on 2015/05/21 23:27:18 UTC

[jira] [Created] (CXF-6419) Update JMSEndpoint properties using EndpointInfo

Andrei Shakirin created CXF-6419:
------------------------------------

             Summary: 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 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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)