Page History

...

Release v7.0

(Scheduled for release Q2 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.
   
   

...