[
https://issues.apache.org/jira/browse/CAMEL-8443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14350108#comment-14350108
]
Jyrki Ruuskanen edited comment on CAMEL-8443 at 3/6/15 8:33 AM:
----------------------------------------------------------------
Yeah, that can be used to set the description (which ends up in
OptionalIdentifiedDefinition), but how do I access it through JMX?
Route JMX operation getDescription() is tied to route.toString() which doesn't
seem to have any connection to OptionalIdentifiedDefinition.getDescription().
was (Author: yuruki):
Yeah, that can be used to set the description (which ends up in
OptionalIdentifiedDefinition), but how do I access it through JMX? Route JMX
operation getDescription() is tied to route.toString() which doesn't seem to
have any connection to OptionalIdentifiedDefinition.getDescription().
> Add properties to route via DSL and XML, expose route properties via JMX
> ------------------------------------------------------------------------
>
> Key: CAMEL-8443
> URL: https://issues.apache.org/jira/browse/CAMEL-8443
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Reporter: Jyrki Ruuskanen
> Priority: Minor
>
> Allow adding arbitrary String properties to a route, with
> .routeProperty(name, value) in Java DSL and <routeProperty name="..."
> value="..."/> in XML.
> Expose getProperties(), getProperty(String name) and setProperty(String name,
> String value) for routes in JMX.
> Our use case:
> Add documentation to route in code and show it on a graph of Camel contexts,
> routes and endpoints in a running system. Graph is generated from JMX data.
> This would be nice data to show on hawtio as well. Although in this case we
> might want to use an explicit documentation variable rather than a reserved
> property name.
> Route has a properties map but that's used internally. These public
> properties would be held in a new map: publicProperties.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
