Hi, I am still thinking about getting the CORS working. It should be possible to get it working by finding the magic configuration between the jetty configuration and the Jolokia one.
However, I really think that the best way to go is to deploy the web app in the jetty folder because it avoids any post install trick. Concerning the Artemis integration, I started to have a look at it, it should be possible to do something but to be honest, I think that the first step would first be to define the kind of methods that must be available by a monitoring console and to make them available via rest calls. For example, if you have a lot of connections, I did not find a way to get all the connection details (Consumers Enqueues/Dequeues) in a single rest call which is far from perfect. Another example is that I did not manage to send a message with a non string header. The stomp protocol cannot do it and the send rest API don't let us do it either. Once the monitoring functions well defined, and available through rest calls, it should be possible to easily code nice consoles using technology like Angular JS. And more than that, people will start to use the same interface to create monitoring consoles customised for their own projects. Before the jolokia API, we used a lot the JMX system which is for me no longer easy nor convenient. Cheers, Arnaud -- View this message in context: http://activemq.2283324.n4.nabble.com/DISCUSS-ActiveMQ-CodeName-Web-Console-tp4694984p4705188.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
