[
https://issues.apache.org/jira/browse/CAMEL-5616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13458504#comment-13458504
]
Claus Ibsen commented on CAMEL-5616:
------------------------------------
Yeah that may be the case, but the patch is IMHO wrong if CDI does not support
the mixed resolution which is that the API on CamelContext is *all* about. That
API is not for a single property lookup by its key.
To lookup by key, then use the properties component, not the CamelContext API.
If config location doesn't matter in CDI, then its simple to configure as you
would set the location to "cdi", eg as we have for "blueprint" etc.
What you need to hook is the PropertiesParser so you can do your CDI lookup
there. The java.util.Properties parameter will just be null in this case. Just
as its not used in the camel-blueprint implementation.
> 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
