You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Ernest Allen (JIRA)" <ji...@apache.org> on 2016/01/04 15:31:39 UTC
[jira] [Updated] (DISPATCH-186) Schema should list entities that
should refer to an annotation
[ https://issues.apache.org/jira/browse/DISPATCH-186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ernest Allen updated DISPATCH-186:
----------------------------------
Summary: Schema should list entities that should refer to an annotation (was: Need a way to distinguish singleton annotation types)
> Schema should list entities that should refer to an annotation
> -----------------------------------------------------------------
>
> Key: DISPATCH-186
> URL: https://issues.apache.org/jira/browse/DISPATCH-186
> Project: Qpid Dispatch
> Issue Type: Improvement
> Components: Console
> Affects Versions: 0.6
> Reporter: Ernest Allen
> Assignee: Ernest Allen
> Priority: Minor
>
> There are two types of annotations in the management schema:
> - those like addrPort that include attributes that are different for each entity
> - those like sslProfile that refer to attributes that should be the same for all entities that are annotated with sslProfile
> Internally, the router will treat both annotation types the same. That is, all the attributes for the annotation will be included in the entity.
> However, for a console, it is desirable to separate out the attributes in sslProfile so that they are entered only once and they apply to each entity that refers to them.
> The JSON schema that is produced by the router should contain enough information so that the attributes that are from an annotation like sslProfile can be identified.
--
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