[
https://issues.apache.org/jira/browse/FELIX-5507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15839003#comment-15839003
]
Carsten Ziegeler commented on FELIX-5507:
-----------------------------------------
Unfortunately I have no clue what the problem is. I think it's definitely not
CA because on that side everything looks fine. And now I tend to agree that it
is not SCR either. At the moment I suspect something wired going on in the
framework. Unfortunately I can't use a debugger in that environment, so it
takes some time to get more info.
Anyways, I would like to have a switch, like with the global extender, that if
enabled switches to use the SCR bundle context to get configuration admin. It
would be off by default
> ConfigurationAdmin not visible to bundles
> -----------------------------------------
>
> 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
> 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
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
