[
https://issues.apache.org/jira/browse/CAMEL-5616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13458499#comment-13458499
]
Łukasz Dywicki commented on CAMEL-5616:
---------------------------------------
Claus,
Way how the properties component is glued with context is one huge hack.
PropertiesResolver API does not match CDI cases, it's influenced by spring
property placeholder stuff (it was replacement for it so I'm not surprised it
looks like original). In CDI you don't care about config location, whatever it
is because config sources are automatically registered by cdi extension. You
ask just about property to resolve (no access from API to grab all properties
with names). Thus even if you will pass location of properties you would like
to load nobody knows what to with it.
> Share properties configuration between CDI and CamelContext
> -----------------------------------------------------------
>
> Key: CAMEL-5616
> URL: https://issues.apache.org/jira/browse/CAMEL-5616
> Project: Camel
> Issue Type: Bug
> Components: camel-cdi
> Reporter: Łukasz Dywicki
> Assignee: Hadrian Zbarcea
> Fix For: 2.11.0
>
> Attachments: CAMEL-5616-new.patch
>
>
> Apache DeltaSpike provides convenient way to inject configuration using
> @ConfigProperty value.
> In ideal world @ConfigProperty injected by deltaspike should be same as
> configuration property visible from Camel Context.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
