You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2016/12/22 17:59:58 UTC

[jira] [Commented] (QPID-6028) [Java Broker] Configured model objects should have only one parent

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

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

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

QPID-6028: [Java Broker] Eliminate model objects with multiple parents.

- Binding no longer a model object.
- Exchange have bindings that are associated with Destinations (routing supports queue at the moment)
- Consumer now has a single parent Queue.
- Bindings refactored

> [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