[
https://issues.apache.org/jira/browse/FELIX-5507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15865572#comment-15865572
]
Karl Pauls commented on FELIX-5507:
-----------------------------------
I tentatively agree with you ([~davidb]) - at least in so far as that as I
said, I think the detection could be (and probably should be) improved and that
it probably should be off by default. However, as regards this specific issue I
do think it is irrelevant as no matter what, it should not be involved in the
assignability check to begin with. Consequently, let me recoin my statement
about further actions as follows:
If nobody complains, I will go ahead and create 3 new issues namely,
1) Set default for implicit bootdelegation to false
2) Improve implicit boot delegation detection
3) Don't take implicit boot delegation into account on service assignability
check
I'll try to get to address 3) asap and get it out with a new Felix release
hopefully this week. This should address this issue at least as far as the
framework is concerned. However, I agree with [~cziegeler] and [~tjwatson]
comments above that there still is an SCR issue as it should (or better must)
use reflection for using the service.
In regard to 1) and 2), I can see 1) being part of a bigger release (Major
bump) sometime later - possible with a release in which we claim compliance
with R7 and we can work on 2) separately and get it out when it is ready.
> 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)
