[
https://issues.apache.org/jira/browse/FELIX-5507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15865481#comment-15865481
]
David Bosschaert commented on FELIX-5507:
-----------------------------------------
Hi [~karlpauls], thanks for the analysis and explaining. I still have the
feeling though that the implicit bootdelegation is too wide. You say that it
was designed for certain JDK/Swing scenarios. If we cannot switch it off by
default (which I think would be a better default) - can we then at least limit
it to certain packages?
> ConfigurationAdmin not visible to bundles
> -----------------------------------------
>
> Key: FELIX-5507
> URL: https://issues.apache.org/jira/browse/FELIX-5507
> Project: Felix
> Issue Type: Bug
> Components: Framework
> Affects Versions: framework-5.6.1
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: framework-5.6.2
>
>
> 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.15#6346)
