THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
This roadmap covers the following Java components:
- Java Broker
- Legacy 0-8..0-10 Java Client
It does not cover the newer Qpid JMS client.
It lists major work items only.
Release v6.0
Scheduled for delivery Q3 2015
Java Broker
- Refactored IO layer and utilize Direct memory for message payload/headers bringing the to ring fence resources such as threads/memory etc (to support use cases where many applications share a single Broker)
- Fully integrate logging into management
AMQP 0-8..0-10 Java Client
- End of end encryption support
Release v6.1
Schedule for delivery: Q4 2015
Java Broker
- Separate Web Management Console.
- Ability to deploy the Web Management Console independently of the Broker and have the ability to manage many Brokers. Use case is for a managed service scenario where an operator is interested in managing many Brokers.
- Ability to delegate authentication to OAUTH2
- Web Management Console will probably be deployed to web container such as Tomcat.
- Real time charting within the Web Management Console
- Ability to draw real time charts of important statistics such as queue depths from within the UI
Other
- System test remediation work. Current system test suite is poorly structured, time consuming to run and requires exclusive use of the machine
- Allow many instances of the system test suite to be run concurrently (i.e. stop assuming certain ports will be available)
- Better test classification mechanism perhaps utilising the facilities of Junit4.
Release v6.2
Schedule for delivery: Q1 2016
Java Broker
- Access Control rework.
- Fully integrate ACLs into the Java Broker's object model
- Allow ACL rules to be changed on the fly without the need to modify files or restart Brokers
- For HA, have the ACL rules applied to a VH automatically replicated around the nodes in the group
- Ability to federate Java Broker
- Start/stop shell/batch script elimination