[jira] [Commented] (FELIX-4176) ScrService should provide method to get Component configuration (if present)
[ 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 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
[jira] [Commented] (FELIX-4176) ScrService should provide method to get Component configuration (if present)
[ https://issues.apache.org/jira/browse/FELIX-4176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13767381#comment-13767381 ] Christoph Läubrich commented on FELIX-4176: --- Hi [~djensen] thanks for looking at this. About the ungetting of CA: Should then the component configuration be resetted to default? Beside this, I would also be happy to just get a Map back. The reason for this is, that for analysis it is somethimes good to know what are the original/actual values and wich are overriden by the cfg, but sure it would also be possible to fetch the Configuration on my own, it is just an extra step and in a secured envirourment I might not be allowed to fetch arbitary configuration objects from my diagnostic bundle! And since the SCR already has all information at hand it seems legal to me to expose that via the 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
[jira] [Commented] (FELIX-4176) ScrService should provide method to get Component configuration (if present)
[ https://issues.apache.org/jira/browse/FELIX-4176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13763687#comment-13763687 ] David Jencks commented on FELIX-4176: - See enterprise 500 spec 104.4.5, the configuration properties include service.pid which is the (possibly targeted) pid of the configuration. I don't think providing a convenience api to get the Configuration object is a good idea. For instance, until recently (and not yet in a released CA version) Configuration objects returned by felix ConfigAdmin didn't work after the config admin service was ungot. I'm going to close this as won't fix unless someone comes up with a really good argument why the api would be a good idea. > 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
