[
https://issues.apache.org/jira/browse/FELIX-4176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13768188#comment-13768188
]
Felix Meschberger commented on FELIX-4176:
------------------------------------------
[~laeubi] I fear you are mixing concerns here.
A component gets its configuration which is a mix of different sources (see the
spec for details). That's all the component is really concerned with. This
configuration can be retrieved from the ComponentContext as a Dictionary or can
be passed into the activate (or modified) method as a Map<String, ?).
Other than that components are not interested to know where this configuration
really comes from. That's none of the business of the component.
If you have diagnostics bundles, those bundles have a very valid reason to
access any configuration for diagnostics purposes and should therefore have
appropriate permissions to access any and all configuration.
In addition, adding a Configuration object to the picture, would in fact create
a Configuration Admin dependency into the DS API, which would bring some
problematic coupling.
So, I agree with [[email protected]] that we should not add such API.
> ScrService should provide method to get Component configuration (if present)
> ----------------------------------------------------------------------------
>
> Key: FELIX-4176
> URL: https://issues.apache.org/jira/browse/FELIX-4176
> Project: Felix
> Issue Type: Improvement
> Components: Declarative Services (SCR)
> Reporter: Christoph Läubrich
> Priority: Minor
>
> Currently the Properties can be quieried, but it is not possible to access
> the configuration the component has currently in use.
> It would be nice if at least the pid can be querried (this is usefull for
> factory configurations).
--
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
