Must have: Support for the Timestamp plugin, or (better) built-in equivalent. My usage requires the ability to override timestamps on submitted messages to correct for out of synch clocks between clients and server.
On Wed, Apr 15, 2015, 8:58 AM James Carman <ja...@carmanconsulting.com> wrote: > In order for ActiveMQ {CodeName} to take over as the next generation > of ActiveMQ, it obviously must have some level of feature parity with > the existing ActiveMQ 5.x (or 6.x if it's released before that > transition) offering. We should come up with some level of a roadmap > together about which features are required. Thus far, the only > big-ticket items that have been addressed are: > > 1. The OpenWire protocol is supported > 2. Auto-creation of destinations (mostly complete). > > This is obviously not all of what the existing ActiveMQ is all about. > What other features are folks wanting to see in the next generation > ActiveMQ? > > James >