[
https://issues.apache.org/jira/browse/CAMEL-5616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13460299#comment-13460299
]
Claus Ibsen commented on CAMEL-5616:
------------------------------------
Lukasz
Yeah the current API is based on the needs back them for people to use
placeholders with Spring and Camel. Later spring-dm and blueprint as well.
It may be that in Camel 3.0 the property placeholder API could warrant an API
in the spi package instead of being based on a Camel component.
Though a Camel component comes very natural to Camel, after all there is 100+
in the box. And for example the bean component could maybe have been
implemented as a EIP instead as a service activator etc.
Lukasz, do you mind helping with documentation as well? I guess a few spots to
add some details about this could be at:
- http://camel.apache.org/cdi
- http://camel.apache.org/properties
- http://camel.apache.org/using-propertyplaceholder.html
> 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-component.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
