felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Felix Meschberger (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FELIX-5507) ConfigurationAdmin not visible to bundles
Date Thu, 26 Jan 2017 08:47:24 GMT

    [ https://issues.apache.org/jira/browse/FELIX-5507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15839427#comment-15839427
] 

Felix Meschberger commented on FELIX-5507:
------------------------------------------

I tend to agree with [~djencks] here. IIRC the reason for using the extended bundle's context
is to make sure the Configuration Admin service applies the correct permissions for the consuming
bundle ! Using the system bundle completely breaks this assumption and I would even go as
far as saying this is non-compliant behaviour.

It really is important to find the real cause for the problem in this context.

> 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)

Mime
View raw message