Return-Path: X-Original-To: apmail-camel-issues-archive@minotaur.apache.org Delivered-To: apmail-camel-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 49456FB97 for ; Fri, 19 Apr 2013 13:35:17 +0000 (UTC) Received: (qmail 18150 invoked by uid 500); 19 Apr 2013 13:35:17 -0000 Delivered-To: apmail-camel-issues-archive@camel.apache.org Received: (qmail 18035 invoked by uid 500); 19 Apr 2013 13:35:16 -0000 Mailing-List: contact issues-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 issues@camel.apache.org Received: (qmail 18003 invoked by uid 99); 19 Apr 2013 13:35:15 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 Apr 2013 13:35:15 +0000 Date: Fri, 19 Apr 2013 13:35:15 +0000 (UTC) From: "Claus Ibsen (JIRA)" To: issues@camel.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (CAMEL-6299) ServiceMBean - Should have an id so its easy to spot what the service is MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Claus Ibsen created CAMEL-6299: ---------------------------------- Summary: ServiceMBean - Should have an id so its easy to spot what the service is Key: CAMEL-6299 URL: https://issues.apache.org/jira/browse/CAMEL-6299 Project: Camel Issue Type: Improvement Components: camel-core, jmx Affects Versions: 2.10.0 Reporter: Claus Ibsen Assignee: Claus Ibsen Priority: Minor Fix For: 2.11.1 Services in Camel such as default inflight registry and others should have an id attribute, with their last part of mbean name. That makes it easier to see what the mbean is, when you list its attributes. Also helps differentiate the services from each other. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira