[
https://issues.apache.org/jira/browse/DISPATCH-186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15081245#comment-15081245
]
ASF subversion and git services commented on DISPATCH-186:
----------------------------------------------------------
Commit 5d0ec672d06eec3d8fee79d7a90e85ba47b1e43a in qpid-dispatch's branch
refs/heads/master from [~eallen]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=5d0ec67 ]
DISPATCH-186: Modify schema to indicate sslProfile should entered separately in
console.
> 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: [email protected]
For additional commands, e-mail: [email protected]
