[
https://issues.apache.org/jira/browse/CAMEL-6552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-6552.
--------------------------------
Resolution: Later
Its pretty flexible today.
Lets close and people can create new tickets if there is any demand but after
looking at latest code
> More dynamic options for properties component locations
> -------------------------------------------------------
>
> Key: CAMEL-6552
> URL: https://issues.apache.org/jira/browse/CAMEL-6552
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Affects Versions: 2.11.0
> Reporter: Daniel Gredler
> Priority: Minor
> Attachments: dynamic-properties-location.patch
>
>
> As part of the properties component, Camel provides abstractions that make it
> easy for third parties to customize its behavior (e.g. {{PropertiesParser}},
> {{PropertiesResolver}}). However, the resolution of properties file locations
> cannot be customized, and file locations cannot be dynamically resolved at
> runtime.
> Additionally, Camel's Spring integration allows {{RouteBuilder}} instances to
> dynamically contribute new routes to the Camel context. However, it is not
> easy to dynamically contribute new properties file locations containing
> configuration for these routes. The result is that while routes can be
> contributed dynamically in a decentralized way, route configuration must be
> centralized.
> The attached patch implements one possible solution to this limitation. It
> adds a new interface ({{PropertiesLocation}}), a default implementation
> ({{DefaultPropertiesLocation}}), and two new methods on the
> {{PropertiesComponent}}: {{setLocation(PropertiesLocation)}} and
> {{addLocation(PropertiesLocation)}}. It also ensures that any
> {{PropertiesLocation}} instances available in the registry (or Spring
> context) are automatically added to the {{PropertiesComponent}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
