[
https://issues.apache.org/jira/browse/CAMEL-22666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18035843#comment-18035843
]
Cameron Fitzwater edited comment on CAMEL-22666 at 11/6/25 2:18 PM:
--------------------------------------------------------------------
[~davsclaus], I do apologize, but I did open this as a *FEATURE* request...
therefore, as a user (who prefers simplicity), I am trying to help improve the
product by creating tickets like these.
Not being able to do this from the `from` level seems a bit inconsistent. As
well as, a lot of the documentation showing route using the shorter syntax of
starting with a `- from:`. It is less intuitive to have to wrap it in a route
to just name it, whereas, we could be doing this within the `- from` by adding
a `routeId`, as you say.
Please give this a bit more consideration, and if warranted reopen for it to be
improved (or if not, maybe some explanation as to why it might not be a good
idea).
was (Author: JIRAUSER310023):
[~davsclaus], I do apologize, but I did open this as a *FEATURE* request...
therefore, as a user (who prefers simplicity), I am trying to help improve the
product by creating tickets like these.
Not being able to do this from the `from` level seems a bit inconsistent. As
well as, a lot of the documentation showing route using the shorter syntax of
starting with a `- from:`. It is less intuitive to have to wrap it in a route
to just name it, whereas, we could be doing this within the `- from` by adding
a `routeId`, as you say.
Please give this a bit more consideration, and if warranted reopen for it to be
improved.
> feat: camel-from - yaml to support an id
> ----------------------------------------
>
> Key: CAMEL-22666
> URL: https://issues.apache.org/jira/browse/CAMEL-22666
> Project: Camel
> Issue Type: New Feature
> Reporter: Cameron Fitzwater
> Priority: Minor
>
> YAML DSL is currently allows "id" inside 'from:' but it appears to be
> silently ignored.
> {code:java}
> - from:
> id: "abc"
> uri: "direct:getABC"
> steps:
> - log: "START"{code}
> Output:
> {code:java}
> Routes startup (total:1)
> Started route1 (direct://getABC){code}
> Setting an identifiers is helpful for metrics (if we n+1 routes, no idea what
> "route1" means). The current workaround seems to be to define it at the route
> level:
> {code:java}
> - route:
> id: "abc"
> from:
> uri: "direct:getABC"
> steps:
> - log: "START"{code}
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
