[
https://issues.apache.org/jira/browse/FELIX-5507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15832233#comment-15832233
]
David Jencks commented on FELIX-5507:
-------------------------------------
what? Why can the system bundle context find any config admins at all? The
purpose of the ConfigAdminTracker is to find the particular config admin
implementation visible to the extended bundle; for instance in IBM Websphere
Liberty the "main" config admin instance is not visible to subsystems, so an
isolated subsystem will have to include it's own config admin implementation in
order to have configuration. If you are using non-Liberty Websphere you may be
running into the non-spec composite bundle way of doing isolation.
> 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)
