qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rob Godfrey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QPID-5615) [Java Broker] Broker and VirtualHost should use the same API for configuration stores
Date Sat, 26 Apr 2014 08:51:17 GMT

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

Rob Godfrey commented on QPID-5615:

ah... forgot to comment on this one:

* org.apache.qpid.server.model.ConfiguredObject.getType() should it have a derived annotation
instead of automate? It does not look that we support type change operation yet. Thus, user
cannot change type through the management interfaces.Also, it might be useful to add type
into actual attributes if it is not there.

I think we *should* be able to change the type eventually - though perhaps not in a way that
would take immediate effect... e.g you could change a standard queue to be a priority queue,
but the change would not take effect until the queue was restarted.  More generally this probably
indicates that there is a type of attribute that can be set (so is not derived) but that the
change is not immediate...

> [Java Broker] Broker and VirtualHost should use the same API for configuration stores
> -------------------------------------------------------------------------------------
>                 Key: QPID-5615
>                 URL: https://issues.apache.org/jira/browse/QPID-5615
>             Project: Qpid
>          Issue Type: Sub-task
>          Components: Java Broker
>            Reporter: Rob Godfrey
>            Assignee: Rob Godfrey
> Currently there are two different interfaces for the persisting of configured object,
one which is used by objects that live directly under the broker, and one which is used by
objects underneath the virtual host.
> The two APIs should be unified, the recovery process should me made generic, and a standardised
way of differentiating between objects which inherit their parents store and those which manage
their own should be made (Broker and VirtualHost should not be special-cased in any store

This message was sent by Atlassian JIRA

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

View raw message