THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Project Goal: Create a multi language Demo for Qpid, and use the demo as source to create the Qpid getting Started pages
Mentor: Carl/Rajith
Project Description:
The Qpid project likes to have an enterprise grade demo that reflects the messaging capabilities of the AMQP (www.amqp.org) protocol that uses brokers written in Java and C++ and the clients written in Java/JMS, c++, python, ruby, .NET
...
AMQP mgmt Bridge - JMX
Candidates: Le Duc Bao,Lahiru Gunathilaka
Project Goal: Create a dynamic bridge from AMQP-mgmt protocol to JMX to facilitate std management console integration
Mentor: Marnie/Aidan/Arnaud ?
Project Description:
Project is to create a process will receive management Data through the AMQP mgmt protocol and translate those into JMX. This will allow the C++ broker to also be hooked into a JMX allow for all the instrumentation data to be read from JMX, all the methods to be invoked, and the configuration to be updated through standard JMX consoles.
...
Project Goal: Create a dynamic bridge from AMQP-mgmt protocol to JMX to facilitate std management console integration
Mentor: Arnaud
Project Description:
Project is to create a process will receive management Data through the AMQP mgmt protocol and translate those into WS-DM This will allow the C++ broker to also 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 like BMC, Tivoli, etc.
...
Implementation language is the choice of the implementor (suggested languages are Python or Java)
JMX Cli
Candidates: Ruchira Wagisha Lahiru Gunathilaka
Project Goal: Provide the ability to access Java Broker mgmt info from cmd line.
Secondary Goal: Integrate with AMQP mgnt protocol ??
Mentor: Adian/Marnie/Martin
Project Description:
Design and implement a simple solution, runnable from the command line, for extracting useful JMX information from the Qpid Java Broker. Solution should be configurable at runtime to allow users to decide which bits of info they're interested in and when. Might be nice to see the information extracted in a report format
...
Project Goal: Rationalize the configuration in the Java Broker to get it more consistent
Mentor: Adian/Marnie/Martin
Project Description:
Refactor Qpid Java Broker configuration into a more elegant xml schema, with xsd, covering all existing configuration options and allowing for extension. Additionally implement a module to validate broker configuration files, which could be run standalone i.e. before starting a broker, to check that they're well formed and validate against the xsd.