[
https://issues.apache.org/jira/browse/QPID-955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12616878#action_12616878
]
Arnaud Simon commented on QPID-955:
-----------------------------------
Hi,
I am looking at apache.zip and I am seeing the following errors:
- ManagementDecoder cannot extend AbstractDecoder as it is not within the same
package
- same for ManagementEncoder
- The above issues being solved, ManagementClient has a type mismatch issue at
line 463
I may not be looking at the right code though.
One question on the code I am looking at:
- why is the run method of ManagementClient infinitely looping creating
destinations?
Arnaud
> WSDM Interface
> --------------
>
> Key: QPID-955
> URL: https://issues.apache.org/jira/browse/QPID-955
> Project: Qpid
> Issue Type: New Feature
> Components: AMQP Compliance, Java Management Console
> Environment: Java, WS-DM Specification
> Reporter: Rahul Mehta
> Attachments: apache.zip, JMX-WSDM.doc, qpid_JMX-WSDM.ppt, README.txt
>
>
> Create a WS-DM (Web Services-Distributed Management) interface that will
> receive management Data through the AMQP mgmt protocol and translate those
> into WS-DM.
> The main objective of introducing this AMQP-WSDM bridge in Apache Qpid is to
> allow any qpid broker to be hooked into any WS-DM console and allow for all
> the instrumentation data to be read, all the methods to be invoked, and the
> configuration to be updated through standard WS-DM console.
> This project will take the schema from AMQP-mgnt and then dynamically expose
> those over JMX and WS-DM. This means that any of the management data from the
> broker can be managed by any JMX console or WS-DM console.
> "Implementation of WSDM specification(s) (Management of Web Service &
> Management Using Web Service ) and integrate this in the Apache Qpid will be
> the major tasks in this project."
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
