[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=15876744#comment-15876744 ] ASF subversion and git services commented on QPID-6028: --- Commit 1783945 from oru...@apache.org in branch 'java/trunk' [ https://svn.apache.org/r1783945 ] QPID-7678,QPID-6028: Revert previous changes as it was a deliberate decision: if message could not be enqueued on all queues it should not be enqueued on any > [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 > > > 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.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[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=15876269#comment-15876269 ] ASF subversion and git services commented on QPID-6028: --- Commit 1783909 from oru...@apache.org in branch 'java/trunk' [ https://svn.apache.org/r1783909 ] QPID-7678,QPID-6028: Fix RoutingResult#send() to allow sending of the message into all acceptable routable queues > [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 > > > 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.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[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=15843091#comment-15843091 ] ASF subversion and git services commented on QPID-6028: --- Commit 1780580 from [~k-wall] in branch 'java/trunk' [ https://svn.apache.org/r1780580 ] QPID-6028: [Java Broker] Ensure queue removal triggers exchange unbind > [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 > > > 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-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[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=15801233#comment-15801233 ] Keith Wall commented on QPID-6028: -- Currently, when viewing links to a Queue within the Management UI, you cannot see where the link originated from. I think Queue#getPublishingLinks should return a Map> instead of a List. > [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 > > > 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-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[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=15783432#comment-15783432 ] ASF subversion and git services commented on QPID-6028: --- Commit 1776316 from oru...@apache.org in branch 'java/trunk' [ https://svn.apache.org/r1776316 ] QPID-6028: Fix binding creation/deletion/listing UI in Web Management Console > [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-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[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=15782711#comment-15782711 ] ASF subversion and git services commented on QPID-6028: --- Commit 1776271 from [~k-wall] in branch 'java/trunk' [ https://svn.apache.org/r1776271 ] QPID-6028: [Java Broker] ManagementNodeConsumer must take a message reference whilst it retains responsibility for the message - fixes NPE exposed by r1776037 > [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-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[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=15777175#comment-15777175 ] ASF subversion and git services commented on QPID-6028: --- Commit 1776037 from [~godfrer] in branch 'java/trunk' [ https://svn.apache.org/r1776037 ] QPID-6028 : allow binding destinations to be things other than queues > [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-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[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=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-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[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=15772644#comment-15772644 ] ASF subversion and git services commented on QPID-6028: --- Commit 1775819 from [~k-wall] in branch 'java/trunk' [ https://svn.apache.org/r1775819 ] QPID-6028 : [Java Broker] PublishingLink is a generalisation of Binding > [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-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[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=15772643#comment-15772643 ] ASF subversion and git services commented on QPID-6028: --- Commit 1775818 from [~k-wall] in branch 'java/trunk' [ https://svn.apache.org/r1775818 ] QPID-6028 : Queue caches binding count > [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-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[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=15772524#comment-15772524 ] ASF subversion and git services commented on QPID-6028: --- Commit 1775810 from [~k-wall] in branch 'java/trunk' [ https://svn.apache.org/r1775810 ] QPID-6028 : Refactor ACO constructors etc to accept only a single parent > [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-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[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=15772352#comment-15772352 ] ASF subversion and git services commented on QPID-6028: --- Commit 1775803 from [~k-wall] in branch 'java/trunk' [ https://svn.apache.org/r1775803 ] QPID-6028 : Prevent ClassCastException causing test failures on persistent profiles > [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-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[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=15771516#comment-15771516 ] ASF subversion and git services commented on QPID-6028: --- Commit 1775781 from [~godfrer] in branch 'java/trunk' [ https://svn.apache.org/r1775781 ] QPID-6028 : Change AbstractConfiguredObject to store only the single parent > [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-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[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=15771337#comment-15771337 ] ASF subversion and git services commented on QPID-6028: --- Commit 1775768 from [~godfrer] in branch 'java/trunk' [ https://svn.apache.org/r1775768 ] QPID-6028 : Change the Model to prevent multiple parents > [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-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[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=15770978#comment-15770978 ] ASF subversion and git services commented on QPID-6028: --- Commit 1775722 from [~k-wall] in branch 'java/trunk' [ https://svn.apache.org/r1775722 ] QPID-6028: [Java Broker] Prevent NPE when unbinding from the fanout exchange. Ensure the AbstractExchange interpretation of bindingKey is uniform across the whole API (that is we always treat a null bindingKey as the empty string). Prevent 0-8..0-91 passing bindingKey "null" when unbinding with null binding key. Fixes QPID-3987 too. > [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-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[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-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
