THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Excel | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
Overall work plan
- Update BDB+Derby message stores to use new configuration storage model, representing ConfiguredObjects in a more generic fashion through storage attributes as JSON rather than specific table columns as at present.
- Maintain existing store interface for now, use a new layer shared between BDB+Derby to convert existing objects into the JSON format stored by the new store schema, allowing later change of the store interface using the same on-disk format.
- Update message content and metadata references to queues to use ids rather than names (allowing queues to be renamed).
- TODO: what about messages for queues that are definied in XML? (Possibly generate UUID based from name (nameUUIDFromBytes(byte[] )
- Refine store upgrade process using a model whereby the broker automatically performs the upgrades between each store version upon startup (inc multiple upgrades spanning version gaps).
- Isolate individual upgrade steps, remove version numbers form the tables and have a version table etc (See Robs patch for example)
- Convert existing messages to use new id-reference to their associated queue.
- Complete implementation of new plugin based JMX MBean adaption layer.
- VirtualHost, Exchange, Queue etc
- Updating of tests as necesssary and/or creation of new unit tests to replace old system tests where possible.
- UserManagement, LoggingManagement MBeans still TBC
- Extract the Operational Logging from the core broker and define as a plugin listening for configuration events.
- (Complete) Definition of the REST management interface
- (Complete) Implementation of the REST management interface
- Design the desired layout for the new web management UI
- Get the basic web management ui running
- Make the ui 'pretty'