Return-Path: Delivered-To: apmail-camel-dev-archive@www.apache.org Received: (qmail 32147 invoked from network); 3 Dec 2010 20:02:32 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 3 Dec 2010 20:02:32 -0000 Received: (qmail 37320 invoked by uid 500); 3 Dec 2010 20:02:32 -0000 Delivered-To: apmail-camel-dev-archive@camel.apache.org Received: (qmail 37294 invoked by uid 500); 3 Dec 2010 20:02:32 -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 37286 invoked by uid 500); 3 Dec 2010 20:02:32 -0000 Delivered-To: apmail-activemq-camel-dev@activemq.apache.org Received: (qmail 37283 invoked by uid 99); 3 Dec 2010 20:02:32 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Dec 2010 20:02:32 +0000 X-ASF-Spam-Status: No, hits=-1998.7 required=10.0 tests=ALL_TRUSTED,URI_HEX X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Dec 2010 20:02:31 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id oB3K2ACk001264 for ; Fri, 3 Dec 2010 20:02:11 GMT Message-ID: <30782940.99311291406530921.JavaMail.jira@thor> Date: Fri, 3 Dec 2010 15:02:10 -0500 (EST) From: "Claus Ibsen (JIRA)" To: camel-dev@activemq.apache.org Subject: [jira] Commented: (CAMEL-3279) Let custom Processor be managed in JMX when implementing ManagementAware MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CAMEL-3279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12966648#action_12966648 ] Claus Ibsen commented on CAMEL-3279: ------------------------------------ I got this working now, but I will improve this even more. I got the JMX pieces capable of letting end users use custom Camel processors and decorate them with the Spring @ JMX annotations and have it implement the ManagementAware interface. Then in the Camel JMX code I will merge together the custom annotations and the default annotations we got on ManagedProcessor. This means you got the default stuff, plus the custom stuff as well in the same MBean. The ugly part is the JMX API is really clumpsy so its a bit of hazzle to merge the stuff together. > Let custom Processor be managed in JMX when implementing ManagementAware > ------------------------------------------------------------------------ > > Key: CAMEL-3279 > URL: https://issues.apache.org/jira/browse/CAMEL-3279 > Project: Camel > Issue Type: Improvement > Components: camel-core > Affects Versions: 2.4.0 > Reporter: Claus Ibsen > Assignee: Claus Ibsen > Priority: Minor > Fix For: 2.6.0 > > > See nabble > http://camel.465427.n5.nabble.com/manage-Camel-Processor-using-JMX-tp3235454p3235454.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.