qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lorenz Quack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QPID-7095) [Java Broker] Add meta data for context variables describing their usage
Date Mon, 28 Mar 2016 10:26:25 GMT

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

Lorenz Quack commented on QPID-7095:

tl;dr: I think this is okay, now! The mechanism is in place but we still need to add the actual

>From reviewing your changes I take the following:
* yes, my understanding of the intended use of {{@ManagedContextDependency}} is correct.
* no, the problem was not that {{doWithAllParents}} considers the type hierarchy instead of
the model hierarchy

I found the last point a bit confusing because the declaration of a default context variable
is a global operation while overriding/setting it is a local operation only affecting children
in the model hierarchy. The code under review is only concerned with the declaration part
not with the setting therefore considering the type hierarchy is fine as long as all are processed

> [Java Broker] Add meta data for context variables describing their usage
> ------------------------------------------------------------------------
>                 Key: QPID-7095
>                 URL: https://issues.apache.org/jira/browse/QPID-7095
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Java Broker
>            Reporter: Rob Godfrey
> Currently there is no way to discover which context variables are used by the broker,
and the description of what they do.  We should add meta data covering this and also provide
this information through the dynamic API docs.

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