MUST HAVE
- JMS 2.0 support would be great (and I know is already included in the
code donation)
-- Virtual topics seem like they can be deprecated/discarded in favor of
shared durable subscriptions
NICE TO HAVE
- Support for existing legacy message stores. A means to convert an
existing legacy store to the new store format would suffice.
- Routing (network connectors) between ActiveMQ {Code Name} and ActiveMQ
5.x brokers.
On Wed, Apr 15, 2015 at 12:29 PM, Daniel Guggi <[email protected]>
wrote:
> correction "Message Destinations" -> "Message Groups"
>
> On Wed, Apr 15, 2015 at 6:27 PM, Daniel Guggi <[email protected]>
> wrote:
>
> > @Configuration format file
> > I as a user wouldn't mind either
> >
> > Features I'd also like to have in v6
> > - Message Destinations (afaik already...)
> > - Virtual Destination/Topics support
> > - and big +1 for "Auto-creation of destinations"
> >
> >
> > On Wed, Apr 15, 2015 at 6:03 PM, Clebert Suconic <
> > [email protected]> wrote:
> >
> >> 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
> >> <[email protected]> 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/[email protected]
> >> http://clebertsuconic.blogspot.com
> >>
> >
> >
>
