It wasn't clear to me if the format of the Configuration file is
really important or not. If I was the user i wouldn't mind.
Users will have to change the configs anyways... things like the
journal will have new settings... paging address... address-settings..
other things.. but if the XML taste is a big thing it could be
revisited.
I just wanted to clear that before we jumped ahead into writing code for it.
On Wed, Apr 15, 2015 at 10:56 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
--
Clebert Suconic
http://community.jboss.org/people/clebert.suco...@jboss.com
http://clebertsuconic.blogspot.com
