Return-Path: X-Original-To: apmail-camel-users-archive@www.apache.org Delivered-To: apmail-camel-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4B1999A33 for ; Wed, 7 Mar 2012 10:31:36 +0000 (UTC) Received: (qmail 70352 invoked by uid 500); 7 Mar 2012 10:31:35 -0000 Delivered-To: apmail-camel-users-archive@camel.apache.org Received: (qmail 70279 invoked by uid 500); 7 Mar 2012 10:31:35 -0000 Mailing-List: contact users-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@camel.apache.org Delivered-To: mailing list users@camel.apache.org Received: (qmail 70269 invoked by uid 99); 7 Mar 2012 10:31:35 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Mar 2012 10:31:35 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [209.85.210.173] (HELO mail-iy0-f173.google.com) (209.85.210.173) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Mar 2012 10:31:27 +0000 Received: by iafj26 with SMTP id j26so11200146iaf.32 for ; Wed, 07 Mar 2012 02:31:06 -0800 (PST) MIME-Version: 1.0 Received: by 10.42.72.130 with SMTP id o2mr1227682icj.8.1331116266122; Wed, 07 Mar 2012 02:31:06 -0800 (PST) Received: by 10.50.10.138 with HTTP; Wed, 7 Mar 2012 02:31:06 -0800 (PST) Date: Wed, 7 Mar 2012 11:31:06 +0100 Message-ID: Subject: Naming of JMX beans From: Alexander Krauss To: users@camel.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQlkQD1O+ktPV/62BX47vM4EbwPi/zJjlMCu7HDqWzo9nrxz0WGXZ28im6DhxiuJka+u+ilg X-Virus-Checked: Checked by ClamAV on apache.org Dear list, when running in an OSGi container (Karaf), the JMX beans generated for Camel contexts are prefixed with the id of the corresponding bundle. This makes it hard to set up external monitoring tools, since I would have to hard-code the bundle id in their configuration, which breaks on each change of the bundle configuration in the container. Is there a way to manually specify the id for the JMX beans for a Camel context/route? This would allow me to work around this problem. Thanks, Alex