[
https://issues.apache.org/jira/browse/FELIX-5507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15870001#comment-15870001
]
Thomas Watson commented on FELIX-5507:
--------------------------------------
You will also have to proxy a configuration listener which can get registered
and found by the CM implementation. I doubt you can use the SCR bundle context
to do such a thing because the CM implementation likely will not see the
listener and besides the framework should disallow it because the listener type
is not going to be the correct type according to the SCR impl. I'm not sure
what context SCR is using for the listener today, but it will likely have to be
using the component bundle's context or some other bundle that the CM
implementation can see and is wired to no CM package or the correct one.
If you decide to do this please have it disabled by default and have an option
to enable it. I fear this complication will be full of bugs for a few releases
until all the kinks worked out. I would not want to have such a corner case
impact the vast majority of users today.
> ConfigurationAdmin might not be visible to SCR implementation
> -------------------------------------------------------------
>
> Key: FELIX-5507
> URL: https://issues.apache.org/jira/browse/FELIX-5507
> Project: Felix
> Issue Type: Bug
> Components: Declarative Services (SCR)
> Affects Versions: scr-2.0.8
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: scr-2.1.0
>
>
> We have one case where the extended bundles do not see the configuration
> admin service. Interestingly the same application runs fine everywhere else,
> but just on a special environment (windows, ibm java inside Websphere) we
> have this problem reproducibly.
> Using the system bundle context instead of the bundle context of the extended
> bundle in ConfigAdminTracker solves the problem.
> Interestingly only the bundles started last (2 out of probably 80) see the
> configuration admin.
> It could also be that a faulty service hook is involved, although I'm not yet
> aware of such a hook
> Update: after some discussion, some issues in the framework have been
> identified, but also the SCR implementation is not 100% correct: as it is
> using the bundle context of the extended bundle, it might get a configuration
> admin which interface is not visible to SCR. Therefore it should revert to
> reflection to access the configuration admin.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
