Thank you all very much for the responses. They have certainly given some inspiration and interesting reading.
I have looked into Jolokia. It looks very promising in some ways, but might not be correct choice for me in others. My main concern is that I would like to hide JMX usage from the REST API user, as I feel JMX is very java specific and might introduce unnecessary overhead to users. In my dream scenario, I user could sit down and write a gui against my API without knowing anything about JMX at all. I am still looking into using jolokia in the control layer vs the standard javax.management.*; javax.management.JMX vs J4pClient is very interesting, but I need to research a bit more. Claus Ibsen. Thank you so much for the github link for hawt.io. This might be a bit more of a camel question than an actual Servicemix question. I do not know, if it warrants its own topic or not. I need to find all available components on my ServiceMix instance. That means all premade components file, timer, direct etc etc, but also all custom components added at runtime. Looking a my locally running ServiceMix instance MBeanServer I found MBean type: org.apache.camel:type=components The only visible components however, are components that have been used. In my case I can only see a file component as I have deployed a route using that component. Is this even possible? Looking through the hawt github, I could only find things related to endpoints: https://github.com/hawtio/hawtio/blob/master/hawtio-web/src/main/webapp/app/camel/js/browseEndpoint.ts How do you handle creating a route. Looking here: https://github.com/hawtio/hawtio/blob/master/hawtio-web/src/main/webapp/app/camel/js/routes.ts You use Camel.addRouteXmlChildren($scope, routeXmlNode, nodes, links, null, 0, 0), which I guess is built on addOrUpdateRoutesFromXml("route in xml form") on a context mbean. How do you inform the user about what components are available for his route? Sorry for the long and perhaps poorly formulated question. Thank you in advance -- View this message in context: http://servicemix.396122.n5.nabble.com/Building-an-external-control-layer-is-JMX-the-right-choice-for-interfacing-and-monitoring-ServiceMix-tp5718933p5718991.html Sent from the ServiceMix - User mailing list archive at Nabble.com.
