...

...

Major Releases

This roadmap covers the following Java components:

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

It does not cover the newer Qpid JMS client.

It lists major work items features only.

...

Release

...

(Delivery Q1 2016)

Java Broker

1. OAUTH2 compatible authentication provider
   1. Use-case is management - ability to delegate authentication to an OAUTH2 based back-end such as Google or Cloud Foundry.
2. REST API extended to support single object queries using  JMS selector style expressions.
   1. Ability to bring back a result set containing a restricted set of a object's attributes.  Do we need derived attributes?
   2. Ability to sort by one or more columns in the result set
   3. Ability to limit a result set to first n rows
3. Web management console
   1. Provide a virtualhost centric web management view
   2. Ability to submit queries and view the results (pagination)
   3. Ability to save queries on a per user basis
   4. Dashboard view?
   5. Real time charting
4. Ability to Federate Java Brokers
5. Upgrade Dojo to 1.11

6. Configured object creation tidy-up.

7. Incremental system test improvements

   1. Messaging system testsuite JMS/JNDI

   2. Ability to run system tests concurrently.

AMQP 0-8..0-10 Java Client

None

Release v6.2

(Delivery Q3 2016)

Java Broker

1. HTTP/AMQP on a single port for both secure and plain connections
2. Make the web management console a separately deployable .war
3. LDAP Groups Provider
   1. Ability to utilise group information from a LDAP compatible directory
4. ACL refactoring (to be defined)
5. High performance message store support encryption at rest

AMQP 0-8..0-10 Java Client

None

Release v7

(Delivery Q4 2016)

Java Broker

1. ACL refactoring (to be defined)
2. Web Management Refresh
   1. Improve usability
3. Embeddable Broker / Remove start-scripts.
   
   1. Better maven integration integration test support
4. Source tree: split Java Broker from Legacy AMQP 0-8..0-10 Client
5. Refactoring: Queue Runner Elimination

Minor Releases

Release v6.0.1

(Delivery Jan/Feb 2016)

Java Broker

v7.0

(Scheduled for release Q4 2017)

1. Targets Java 1.8
2. Mature the existing AMQP 1.0 layer (QPID-7531)
3. JMS v2.0 support
   1. Shared Subscriptions (QPID-7569/QPID-7540/QPID-3953)
   2. Delivery Delay (QPID-7568)
   3. Maximum Delivery Count/Dead-lettering (QPID-7603)
   4. Consumer Priority for AMQP 1.0 (Broker support already in place, but Qpid JMS Client lacks the ability to allow properties to be set on link established). (deferred for future release)
   5. Arrival Time Filtering for AMQP 1.0 (QPID-7604) (deferred for future release)
   6. Producer Flow Control (QPID-7529)
   7. Client ID validation (QPID-7605)
   8. System test suite refactored to operate against both Qpid JMS Client and Legacy Client.
      1. There will need to be provision for some tests to be JMS 2.0 only.  How will this be handled (separate module?)
4. Mature the message conversation layer between protocols (QPID-7434)
   1. Fidelity with application headers (need rules around handling of long names, names containing illegal characters or values outside the domain permitted)
   2. Fidelity application payloads including structured payloads (lists/maps etc)
   3. Reply-to conversion supporting request/response across protocol (QPID-7602)
5. VH-centric REST API and VH-centric web management console (the former included, the latter deferred for future release) 
6. Simple REST API compatibility layer (deferred)
7. 'Queue runner' removal - not user facing -  simplifies threading model behind message delivery to queues within the Broker.
8. Model change to remove the requirement for multi-parents (QPID-6028) - not user facing - simplifies the object model underpinning the Broker.
   
   

...

Release v7.1

(Scheduled for release Q3/4 2017)

Qpid Broker for Java

• Replacement for the BDB JE based store with a store offering similar performance characteristics.
• ACL provider replacement
  
  

...

Minor Releases

Release v6.0.7

Not yet planned

Release v6.1.2

Not yet planned.

...