camel-dev mailing list archives

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

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:
http://camel.465427.n5.nabble.com/file/n5717440/threadresource.png 

- table of thread pools data:
http://camel.465427.n5.nabble.com/file/n5717440/threadsresource.png 

- consumers data:
http://camel.465427.n5.nabble.com/file/n5717440/consumersresource.png 

github link:
https://github.com/michalwarecki/camel/tree/trunk/components/camel-web

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.).

Cheers,
Michal



--
View this message in context: http://camel.465427.n5.nabble.com/Camel-Web-Roadmap-tp5717234p5717440.html
Sent from the Camel Development mailing list archive at Nabble.com.

Mime
View raw message