[
https://issues.apache.org/jira/browse/CAMEL-12463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16475355#comment-16475355
]
ASF GitHub Bot commented on CAMEL-12463:
----------------------------------------
davsclaus commented on a change in pull request #2339: CAMEL-12463: camel-core:
allow to add metadata/properties to a route
URL: https://github.com/apache/camel/pull/2339#discussion_r188179318
##########
File path: camel-core/src/main/java/org/apache/camel/model/RouteDefinition.java
##########
@@ -1167,6 +1186,19 @@ public OutputTypeDefinition getOutputType() {
return this.outputType;
}
+ public List<PropertyDefinition> getRouteProperties() {
+ return routeProperties;
+ }
+
+ /**
+ * Set route properties to use.
Review comment:
Improve this javadoc a bit - I think it may be the javadoc that the tooling
grabs for documentation in the XML DSL
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> camel-core: allow to add metadata/properties to a route
> -------------------------------------------------------
>
> Key: CAMEL-12463
> URL: https://issues.apache.org/jira/browse/CAMEL-12463
> Project: Camel
> Issue Type: New Feature
> Components: camel-core
> Reporter: Luca Burgazzoli
> Assignee: Luca Burgazzoli
> Priority: Minor
> Fix For: 2.22.0
>
>
> Routes have
> [properties|https://github.com/apache/camel/blob/master/camel-core/src/main/java/org/apache/camel/Route.java#L88]
> but it is not exposed to the DSL so it is not possible to add arbitrary
> meatadata to a route.
> Having such option is useful for some use cases:
> - cloud related service registration: information added to a route as
> metadata can be used to automatically expose a route as a service in a cloud
> environment (consul, etcd, k8s, spring-cloud)
> - property resolution could also take into account properties/metadata bound
> to a route, this is useful when the route is automatically generated so the
> same property but with different value can be used by different routes.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
