Strategy for assigning the name part of the {@link javax.management.ObjectName}for a managed {@link org.apache.camel.CamelContext}.
A strategy is needed as you can run multiple CamelContext in the same JVM, and want them to be enlisted in the JVM wide JMXMBeanServer. And this requires a strategy to be able to calculate unique names, in case of clashes. Or to enforce an explicit fixed name, to ensure the JMX name is not using dynamic counters etc.
This strategy supports a naming pattern which supports at least the following tokens
- #camelId# - the camel id (eg the camel name)
- #name# - same as #camelId#
- #counter# - an incrementing counter
@see CamelContextNameStrategy
@see org.apache.camel.impl.DefaultManagementNameStrategy