I will call it 2.1 as it has a few features included. Adding feature means bump it. Only fix is minor.
But it's totally compatible with 2.0. On Thu, May 4, 2017 at 1:30 PM Clebert Suconic <clebert.suco...@gmail.com> wrote: > There is a pending PR that I am waiting maven central to sync with the > required component. > > I will start it tonight if everything ok. > > > On Thu, May 4, 2017 at 1:13 PM mtod <m...@thetods.net> wrote: > >> The filtering or routing could be a camel microservice (I have this >> working >> on docker AWS today) or I can work up something using the >> https://activemq.apache.org/artemis/docs/1.0.0/wildcard-routing.html >> >> Our current ActiveMQ uses a Camel content router for managing queue to >> topics. We setup a single input queue for each application then use camel >> to >> route the messages based on a route element in the message header. This >> keeps the number of application connections down and in case of a queue >> corruption should not affect other consumers. We are using ActiveMQ in an >> event based message model today. >> >> But the final method is still an open question. >> >> I'm still working on getting the architectural model up and running so I >> can >> refine the routing and security requirements. >> >> btw when will the 2.0.1 release be out? >> >> Thanks >> >> Mike >> >> >> >> -- >> View this message in context: >> http://activemq.2283324.n4.nabble.com/Artemis-production-ready-tp4725363p4725618.html >> Sent from the ActiveMQ - User mailing list archive at Nabble.com. >> > -- > Clebert Suconic > -- Clebert Suconic
