qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alan Conway (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DISPATCH-102) Provide qdrouter schmea via management interface
Date Wed, 04 Feb 2015 03:14:34 GMT

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

Alan Conway commented on DISPATCH-102:

The following commits were labelled DISPATCH-103 by mistake, they are for this JIRA:

Commit 1655398 from Alan Conway in branch 'dispatch/trunk'
[ https://svn.apache.org/r1655398 ]

DISPATCH-103: Add management entity providng get-schema operations.

    Add org.amqp.management to qdrouter schema.
    Add org.apache.qpid.dispatch extending org.amq.management with get-schema operations
    Make org.amqp.management a regulary entity class, move standard mgmt ops Agent to ManagementEntity.
    Add tests for get-schema operations.

Commit 1656982 from Alan Conway in branch 'dispatch/trunk'
[ https://svn.apache.org/r1656982 ]

DISPATCH-103: Add operation definitions to management schema.

    Operations in schema and schema doc
    Change type names in schema to lower case, consistent with AMQP spec.
    Refactor schema documentation generation code for better re-use, remove dead code..
    Improvements to docstrings
    Added get-json-schema to qdmanage.
    Extend qdmanage to handle non-standard ops.

> Provide qdrouter schmea via management interface
> ------------------------------------------------
>                 Key: DISPATCH-102
>                 URL: https://issues.apache.org/jira/browse/DISPATCH-102
>             Project: Qpid Dispatch
>          Issue Type: Improvement
>          Components: Management Agent
>    Affects Versions: 0.3
>            Reporter: Alan Conway
>            Assignee: Alan Conway
>             Fix For: 0.4
> Provide a management operation that allows a client to download the qdrouter management
schema. The schema should be available in two forms:
> - as an AMQP map
> - as an AMQP string containing a JSON map 
> The goal is to allow consoles and other tools to get the correct schema version from
the running router without needing to co-ordinate installation of matching schema files, e.g.
for a browser-based console.
> The AMQP management specification provides standard operations (GET-OPERATIONS, GET-ATTRIBUTES
etc.) that provide a subset of the schema in a standard way but extension will allow qdrouter-specific
tools to  avail of the full schema (including docstrings)

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