GSoC 2009 Progress
Work is progressing in line with expectations, with several sections of the new UI mostly completed and work underway on the remaining large sections. The table below gives an overview of current progress and areas identified for future implementation efforts.
| Issue # |
Description |
% Complete |
Notes |
| QPID-1926 |
make qpid-management-common an OSGI bundle |
100 |
Done, to be merged to trunk |
| QPID-1927 |
move JMX MBean interface definitions to management-common |
100 |
Done, to be merged to trunk |
| QPID-1928 |
remove Queue MBean reliance on AMQException for unused throws clause |
100 |
Done, to be merged to trunk |
| QPID-1929 |
create a factory class to generate the views for the various MBeans |
90 |
Initial implementation being added to for each subsequent view |
| QPID-1930 |
create a new view for the User Management mbean |
90 |
layout tweaking and explicit reporting of results to do |
| QPID-1931 |
create a new view for the Logging Management mbean |
90 |
layout tweaking and explicit reporting of results to do |
| QPID-1942 |
create a new queue / exchange / connection selection view |
90 |
layout tweaking to do |
| QPID-1945 |
create a new view for the VirtualHostManager mbeans |
90 |
Needs exchange types offered from broker instead of using default list, explicit results reporting to do |
| QPID-1943 |
create a new view for the Exchange mbeans |
40 |
Initial effort did not take into account the headers exchange returning completely different results for viewing bindings and will be redone, with further changes to accomodate upcoming statistics and be more consistent with the Queue and Connection mbean views |
| QPID-1944 |
create a new view for the Connection mbeans |
90 |
layout tweaking and explicit reporting of results to do |
| QPID-1932 |
create a new view for the Queue mbeans |
60 |
initial effort requires reworking to accommodate new way of moving messages, and sorting issues with 'delete message from top' |
| QPID-1941 |
moved messages remain listed on original queue when viewing messages using JMX, but are not actually considered to still be on the queue |
0 |
|
| QPID-1946 |
add an mbean to present system information, including API versioning for the JMX interface |
0 |
|
| QPID-1966 |
add status bar for feedback reports |
0 |
|
| QPID-1947 |
enable automated update to negate need for users to manually refresh the data |
60 |
Refresh mechanism and toolbar addition completed, however it is currently unable to positioned as desired: it may be required to redo existing toolbar icons programatically instead of declaratively. Also requires updates to mbean views to rectify focus issues. |
| QPID-1969 |
per-virtualhost notification areas show all notifications sent by the server |
0 |
|
| QPID-1967 |
gather list of available exchange types from broker instead of hardcoding in console |
0 |
|
| QPID-1961 |
widen viewMessages(int From, int To) and getMessageCount() AMQQueueMBean methods to use Long values |
0 |
|
| QPID-1968 |
add ability to delete arbitrary message from queue |
0 |
|
Weeks 7,8,9
Work will be completed in the next week on the 3 large remaining areas of new UI, the Exchange / Connection / Queue mbean views. Following this, attention will be directed to the broker, specifically QPID-1941, as this is an issue that can severely confuse users as to what content is on the queue and will be deleted upon request, and so should be resolved for the 0.6 release. Additionally, the System Information mbean will be put in place to allow versioning the JMX API presented by the broker in future to preserve compatibility. Following this, work will be completed on polishing the new UI for the existing API, implementing final features such as automated updates and a status bar for feedback reports, and squashing some long standing bugs such as the notifications areas in each virtualhost showing all server-wide notifications. Finally, work will progress onto refining the JMX API offered by future brokers by expanding the scope of the viewMessages() method and related attributes, enabling the list of exchange types to be presented by the broker itself, and adding the ability to delete arbitrary messages rather than only the first message on a queue. Additionally, consideration will be made for the presentation of planned status updates / statistics additions to the broker.
