qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QPID-6028) [Java Broker] Configured model objects should have only one parent
Date Fri, 23 Dec 2016 14:26:58 GMT

    [ https://issues.apache.org/jira/browse/QPID-6028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15773006#comment-15773006
] 

ASF subversion and git services commented on QPID-6028:
-------------------------------------------------------

Commit 1775841 from [~k-wall] in branch 'java/trunk'
[ https://svn.apache.org/r1775841 ]

QPID-6028 : [Java Broker] Fix failing BDBUpgradeTest

> [Java Broker] Configured model objects should have only one parent
> ------------------------------------------------------------------
>
>                 Key: QPID-6028
>                 URL: https://issues.apache.org/jira/browse/QPID-6028
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Java Broker
>            Reporter: Rob Godfrey
>            Assignee: Keith Wall
>             Fix For: qpid-java-7.0.0
>
>
> Currently it is possible for a configured object to be defined as having multiple parents
(of different classes)
> Thus a binding has a "queue" parent and an "exchange" parent, a consumer has a "session"
parent and a "queue" parent, a virtualhostalias has a "port" parent and a virtialhost parent.
> This design should be changed.
> h5. Bindings
> Bindings should have a single exchange parent with the queue being an attribute (note
that this probably also requires adding binding-key as an attribute and setting the name to
queue/binding-key or some such.  Exchange-wide validation on the binding-key will be required)
> h5. Consumers
> Since in AMQP 1.0 a link endpoint may outlive the session that created it, it makes sense
for the parent of the Consumer to be the Queue.  The Session will be a (derived) attribute
of the Consumer.
> h5. VirtualhostAliases
> The primary parent of the virtualhostalias should be the (amqp) port.  The virtualHost
should be an attribute.  On creating a VirtualHost we should offer to create an alias for
the virtual host on all existing ports with the host name as the alias.  On creating a port
we should offer to create aliases for each of the existing virtualhosts.



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

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


Mime
View raw message