qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Rudyy (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (QPID-7965) [Java Broker] Centralise setting of connection properties, and allow pluggable enrichment
Date Thu, 19 Oct 2017 11:54:00 GMT

     [ https://issues.apache.org/jira/browse/QPID-7965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Alex Rudyy resolved QPID-7965.
------------------------------
    Resolution: Fixed

The changes look good to me, though, in {{StandardConnectionPropertyEnricher#addConnectionProperties}}
for switch default case I would log warning or throw an exception. Taking that new protocol
support will not be added anytime soon, I am fine with the code in its current state

> [Java Broker] Centralise setting of connection properties, and allow pluggable enrichment
> -----------------------------------------------------------------------------------------
>
>                 Key: QPID-7965
>                 URL: https://issues.apache.org/jira/browse/QPID-7965
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Java Broker
>            Reporter: Rob Godfrey
>            Assignee: Rob Godfrey
>         Attachments: QPID-7965.diff
>
>
> Currently the setting of connection properties is done differently for each protocol
version, with much overlap.  We could centralise these into a common service; and also allow
for the configuration of pluggable property enrichment (to allow users to set custom properties
for their broker which will be meaningful for their clients).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org


Mime
View raw message