You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2017/02/01 06:11:51 UTC
[jira] [Commented] (FELIX-5507) ConfigurationAdmin not visible to
bundles
[ https://issues.apache.org/jira/browse/FELIX-5507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15848056#comment-15848056 ]
Carsten Ziegeler commented on FELIX-5507:
-----------------------------------------
[~rickhall] Thanks, ok I see. So how can we solve this?
I'm wondering if the current behaviour is in accordence with the spec. The boot delegation property is not listing the org.osgi.service.cm package, but still it is loaded from there. We also set "org.osgi.framework.bundle.parent" to "framework".
I'm not quiet sure, but I'm a little bit confused by the implementation of ServiceReferenceImpl#isAssignableTo. For Case 1 where both requester and provider have no wire, it tries to load the class using delegation anyway - at the moment I don't understand why this is done. Wouldn't it be enought to grant access and assume the class of the registration is used?
> 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)