Return-Path: X-Original-To: apmail-camel-dev-archive@www.apache.org Delivered-To: apmail-camel-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2AB6C90C9 for ; Wed, 15 Aug 2012 17:25:22 +0000 (UTC) Received: (qmail 33682 invoked by uid 500); 15 Aug 2012 17:25:21 -0000 Delivered-To: apmail-camel-dev-archive@camel.apache.org Received: (qmail 33613 invoked by uid 500); 15 Aug 2012 17:25:21 -0000 Mailing-List: contact dev-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@camel.apache.org Delivered-To: mailing list dev@camel.apache.org Received: (qmail 33605 invoked by uid 99); 15 Aug 2012 17:25:21 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 15 Aug 2012 17:25:21 +0000 X-ASF-Spam-Status: No, hits=2.0 required=5.0 tests=SPF_NEUTRAL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: 216.139.236.26 is neither permitted nor denied by domain of michal.warecki@gmail.com) Received: from [216.139.236.26] (HELO sam.nabble.com) (216.139.236.26) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 15 Aug 2012 17:25:17 +0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1T1hKy-00050e-Mb for dev@camel.apache.org; Wed, 15 Aug 2012 10:24:56 -0700 Date: Wed, 15 Aug 2012 10:24:56 -0700 (PDT) From: "michal.warecki" To: dev@camel.apache.org Message-ID: <1345051496680-5717440.post@n5.nabble.com> In-Reply-To: <1344929720531-5717291.post@n5.nabble.com> References: <1344860549041-5717234.post@n5.nabble.com> <1344862713573-5717238.post@n5.nabble.com> <1344864181103-5717241.post@n5.nabble.com> <1344929720531-5717291.post@n5.nabble.com> Subject: Re: Camel Web Roadmap MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org 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.