[
https://issues.apache.org/activemq/browse/CAMEL-3087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61497#action_61497
]
Claus Ibsen commented on CAMEL-3087:
------------------------------------
No problem.
Yeah we had issues in the past in the Java DSL to assign id to the routes,
because {{id}} will clash with setting id on each of the processors in the
route. Hence why we created {{routeId}} to be used for setting the route id.
And therefore we don't have clashes/issues anymore.
> the route name exposed in JMX uses not the route id in some situations
> ----------------------------------------------------------------------
>
> Key: CAMEL-3087
> URL: https://issues.apache.org/activemq/browse/CAMEL-3087
> Project: Apache Camel
> Issue Type: Bug
> Components: jmx
> Affects Versions: 2.2.0
> Environment: apache-servicemix-4.2.0-fuse-02-00 which uses
> camel-2.2.0-fuse-02-00
> Reporter: Christian Mueller
> Assignee: Claus Ibsen
> Fix For: 2.5.0
>
>
> All of our routes are defined in the following way:
> {code:java}
> from("direct:start").id(MyRoute.class.getName() + ".main")
> ...
> .to("mock:result");
> {code}
> but in some situations, the route name exposed in JMX is "routeX" instead of
> "com.company.MyRoute.main"
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
