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

Posted to dev@qpid.apache.org by "Alex Rudyy (JIRA)" <ji...@apache.org> on 2014/08/25 15:54:59 UTC

[jira] [Resolved] (QPID-6034) Refactor Port UI to use metadata service rather than hard-coding a list of protocols/transports etc

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

Alex Rudyy resolved QPID-6034.
------------------------------

       Resolution: Fixed
    Fix Version/s: 0.31

The changes look good to me

> Refactor Port UI to use metadata service rather than hard-coding a list of protocols/transports etc
> ---------------------------------------------------------------------------------------------------
>
>                 Key: QPID-6034
>                 URL: https://issues.apache.org/jira/browse/QPID-6034
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Java Broker
>            Reporter: Andrew MacBean
>            Assignee: Alex Rudyy
>             Fix For: 0.31
>
>
> Refactor the Port UI to use the metadata service (QPID-6009) to determine the list of protocols and transports suitable for each type. 
> Remove want client auth/need client auth attributes from the JMXPort configured object and move the bindingAddress attribute from parent to AMQP and HTTP ports only.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

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