camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "michal.warecki" <>
Subject Re: Camel Web Roadmap
Date Wed, 15 Aug 2012 17:24:56 GMT

I commited an example of two REST resources with html pages which are using
direct JMX client in web console:

- particular thread pool data with "real-time" chart: 

- table of thread pools data: 

- consumers data: 

github link:

Currently connectors support only JMX but CamelConnection can be implemented
in multiple ways.

I saw Lars post about using Jolokia as a JMX http proxy but I'm still have
doubts about it. Direct proxy makes REST full-JMX dependent and does not
allow for additions/modifications.

Please review the code and share your comments. If it suites to Camel
assumptions I can modify current resources (endpoint, routes, languages) and
further develop console (i.e. memory monitoring etc.).


View this message in context:
Sent from the Camel Development mailing list archive at

View raw message