You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Fraser Adams (Created) (JIRA)" <ji...@apache.org> on 2011/12/19 14:43:30 UTC
[jira] [Created] (QPID-3696) C++ broker ManagementAgent currently
only supports QMF2 _what = "OBJECT" queries. This is a patch to add support
for OBJECT_ID, SCHEMA_ID and SCHEMA queries.
C++ broker ManagementAgent currently only supports QMF2 _what = "OBJECT" queries. This is a patch to add support for OBJECT_ID, SCHEMA_ID and SCHEMA queries.
-------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: QPID-3696
URL: https://issues.apache.org/jira/browse/QPID-3696
Project: Qpid
Issue Type: New Feature
Components: C++ Broker
Affects Versions: 0.12
Environment: All
Reporter: Fraser Adams
Priority: Minor
C++ broker ManagementAgent currently only supports QMF2 _what = "OBJECT" queries.
This is a patch to add support for OBJECT_ID, SCHEMA_ID and SCHEMA queries.
The "SCHEMA" query support makes use of the QMF1 schema information already provided for each Management Object and "transcodes" the info into QMF2 Map message format.
The main reason that I took this approach is that I'm not familiar with the schema code generation stuff, so I couldn't generate a "mapEncodeSchema()" method for each Management class, however as it happens That approach would also need changes to registerClass(), registerEvent(), SchemaClass and a few other places because things are a bit tied to the QMF1 writeSchemaCall signature so doing the transcoding is least disruptive to the existing code base and the scope of changes to support the feature are limited to ManagementAgent::handleGetQueryLH() though to be fair that's getting quite big now so it might be worth decomposing it into some smaller methods.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] [Updated] (QPID-3696) C++ broker ManagementAgent currently
only supports QMF2 _what = "OBJECT" queries. This is a patch to add support
for OBJECT_ID, SCHEMA_ID and SCHEMA queries.
Posted by "Fraser Adams (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-3696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Fraser Adams updated QPID-3696:
-------------------------------
Attachment: mgmt-agent-qmf2-schema-support.patch
> C++ broker ManagementAgent currently only supports QMF2 _what = "OBJECT" queries. This is a patch to add support for OBJECT_ID, SCHEMA_ID and SCHEMA queries.
> -------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: QPID-3696
> URL: https://issues.apache.org/jira/browse/QPID-3696
> Project: Qpid
> Issue Type: New Feature
> Components: C++ Broker
> Affects Versions: 0.12
> Environment: All
> Reporter: Fraser Adams
> Priority: Minor
> Attachments: mgmt-agent-qmf2-schema-support.patch
>
>
> C++ broker ManagementAgent currently only supports QMF2 _what = "OBJECT" queries.
> This is a patch to add support for OBJECT_ID, SCHEMA_ID and SCHEMA queries.
> The "SCHEMA" query support makes use of the QMF1 schema information already provided for each Management Object and "transcodes" the info into QMF2 Map message format.
> The main reason that I took this approach is that I'm not familiar with the schema code generation stuff, so I couldn't generate a "mapEncodeSchema()" method for each Management class, however as it happens That approach would also need changes to registerClass(), registerEvent(), SchemaClass and a few other places because things are a bit tied to the QMF1 writeSchemaCall signature so doing the transcoding is least disruptive to the existing code base and the scope of changes to support the feature are limited to ManagementAgent::handleGetQueryLH() though to be fair that's getting quite big now so it might be worth decomposing it into some smaller methods.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org