[ 
https://issues.apache.org/jira/browse/CAMEL-13947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16937974#comment-16937974
 ] 

Claus Ibsen commented on CAMEL-13947:
-------------------------------------

Renaming the api in camel-api from PropertiesComponent to PropertiesService
PropertiesComponent in camel-properties should then be renamed to 
DefaultPropertiesService

> Create a configuration service instead of leveraging the properties component
> -----------------------------------------------------------------------------
>
>                 Key: CAMEL-13947
>                 URL: https://issues.apache.org/jira/browse/CAMEL-13947
>             Project: Camel
>          Issue Type: Improvement
>          Components: came-properties, camel-core
>            Reporter: Luca Burgazzoli
>            Assignee: Claus Ibsen
>            Priority: Major
>             Fix For: 3.0.0, 3.0.0.RC2
>
>
> As today the way camel resolves properties/configuration is trough the 
> Properties Component which leads to a chicken and egg problem as:
> - camel core depends on properties component
> - the properties component depends on camel core
> We should probably have a proper configuration service part of camel core 
> that can eventually be leveraged by the Properties Component.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to