Major Releases

This roadmap covers the following Java components:

• Qpid Broker for Java
• Legacy 0-8..0-10 Java Client

It does not cover the newer Qpid JMS client.

It lists major features only.

Release v6.1

(Scheduled for release Q3 2016)

Qpid Broker for Java

1. Management features
   1. Support for configured object queries using JMS selector style expressions – allows an operator to better understand a Broker's operation (e.g. show me queue depths for all queues on this virtualhost).
   2. Web Management Console extension to allow queries to be edited/saved/retrieved and simple dashboards (comprising one or more saved queries)
   3. Ability to persist user-preferences at the Broker and Virtualhost level (for replication within a HA group)
2. Authentication / Access Control
   1. Support for LDAP Groups (QPID-7116)
   2. Allow ACLs to be applied at Virtualhost level (for replication within a HA group)
   3. Caching of authentication results to reduce load on back end authentication providers (such as an LDAP Open Directory)
3. Web Management Console
   1. Implement UIs for End to End Encryption (QPID-7037/QPID-7036), OAuth2 ( QPID-7112 / QPID-7111 ) and Virtual Host Aliases (QPID-7110)
   2. Improve UI performance when monitoring large deployments.
4. TLS Cipher suite ordering in order to make use of faster ciphers available JDK 1.8 (QPID-7113)
   
   

Release v6.2

Qpid Broker for Java

1. Extension to allow easy deployment of Brokers in 'common configurations profiles'
   1. This will allow a user to define one or more common configuration profiles used at deployment time to ensure that many Brokers are deployed in the same way to the same standard
   2. It is envisaged that this feature will be used to define 'hardened profiles' such as an "LDAP with TLS transport for messaging/management".
   3. This might involve some kind of manual configuration interrogation during first run ('give me your path to TLS cert' etc) and options  to integrate with systems such as Puppet.
2. Access Control
   1. New access control provider whose rules are associated with the configured objects themselves.
   2. UI fo the new access control provider.
   3. Define at a metalevel how permissions 'role-up' for instance a user with permission to consume and publish to queue might be consider to automatically have the move message permission,
   4. Define how permissions inherit 
3. Make user identity unique (QPID-7092)
4. Gracefully close TLS connections (QPID-6991)
5. Improve verification of the recipient's certificate used for Message Encryption (QPID-7309)
6. Impose absolute time limit on the WMC session 

Release v7.x

(2017)

Qpid Broker for Java

1. HTTP/AMQP on a single port for both secure and plain connections
2. Make the web management console a separately deployable .war
3. Virtualhost centric web management view
4. High performance message store support encryption at rest
5. Ability to Federate Java Brokers
6. REST API compatibility layer (QPID-6948)

7. Configured object creation tidy-up.

8. Message chunking / AMQP message segment capable store (QPID-6766)
9. Web Management Refresh (Angular??)
10. Embeddable Broker / Remove start-scripts.
    
    1. Better maven integration integration test support
11. Source tree: split Java Broker from Legacy AMQP 0-8..0-10 Client
12. Refactoring: Queue Runner Elimination

AMQP 0-8..0-10 Java Client

None

Minor Releases

Release v6.0.1

(Delivered Feb 2016 )

Java Broker

Defect fix release and minor enhancements to aid compatibility. 

Release v6.0.2

(Delivered Apr 2016)

Java Broker

Defect fix release

Release v6.0.3

(Delivered May 2016)

Release v6.0.4

(Delivered Jul 2016)

Release v6.0.5

(Delivery date not yet know)