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

Reply via email to