The web console doesn't work with Jetty disabled, and this doesn't work with Jolokia disabled. Is the difference between those two statements really as big as you've made it out to be?
The simple fact of having some well-documented dependencies doesn't seem like a deal-breaker to me... Tim On Dec 4, 2015 1:52 PM, "artnaseef" <a...@artnaseef.com> wrote: > I like the look-and-feel of this console, based on the screen-shots at > https://github.com/snuids/AMQC/wiki. > > It's very interesting that this tool works entirely out of the browser as > well. > > All of the information displayed is obtained via jolokia, is that correct? > And all administration also operates via jolokia? > > That would be a concern for a web-console, in my opinion, which should work > with any configuration of ActiveMQ, even when jolokia is disabled. With > that said, even if this is not great as a web-console, it is a welcome tool > for ActiveMQ users. > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/ActiveMQ-web-console-tp4704522p4704622.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
