[
https://issues.apache.org/jira/browse/QPID-6443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14566124#comment-14566124
]
ASF subversion and git services commented on QPID-6443:
-------------------------------------------------------
Commit 1682631 from [~k-wall] in branch 'java/trunk'
[ https://svn.apache.org/r1682631 ]
QPID-6443: [Java Broker] Replace the defaultVirtualHost (at Broker) with
defaultVirtualHostNode flag (at VHN)
* Moved attribute from Broker to VirtualHostNode
* Updated broker store upgrader to upgrade older config (if possible)
* Updated the UI - user now uses Edit VHN function to update the flag. VHN/VH
table on the Broker tab now shows the default VHN
> Broker should have a default VHN rather than default VH
> -------------------------------------------------------
>
> Key: QPID-6443
> URL: https://issues.apache.org/jira/browse/QPID-6443
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Reporter: Keith Wall
>
> Currently the Java Broker has a concept of default virtual host, that is, the
> virtual host to which the a client will connect if they don't specify a
> virtual host name in the connection url.
> Since the introduction if the VHN, the concept of default virtual host is
> flawed.
> If a virtual host node is stopped, the underlying VH does not exist, so its
> name is not known to the Broker. If I try to edit the Broker's attributes
> whilst a VNH is stopped, and it happens that the default VH refers to it, the
> dialogue box contain the default virtual host drop down gets confused as it
> tries to present a virtual host name that does not exist in the drop down.
> This forces the user to make a change they do not want.
> Brokers should have a default VHN, rather than VH.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
