We will just stick to XML...
We were looking at how we load configurations and I thought we would be able to do something cool without burning resources... We have a lot on our plate as is already... so I would rather do something cool that would reflect on the broker runtime than spending time on supporting multiple formats... so we gave up on this task :) On Wed, Jan 7, 2015 at 3:32 PM, jgenender <jgenen...@apache.org> wrote: > Yep, I agree with Chirino. That said, there is nothing wrong with supporting > multiple types. but I would definitely ensure that XML is a first class > citizen. > > Jeff > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/activemq6-XML-or-Not-on-Configurations-tp4688999p4689611.html > Sent from the ActiveMQ - Dev mailing list archive at Nabble.com. -- Clebert Suconic http://community.jboss.org/people/clebert.suco...@jboss.com http://clebertsuconic.blogspot.com
