[
https://issues.apache.org/jira/browse/FELIX-5507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15838439#comment-15838439
]
Carsten Ziegeler commented on FELIX-5507:
-----------------------------------------
I did some further investigation, the CA api package is only exported by the
Apache Felix implementation, only a single CA service is registered.
The extended bundle have no import of the CA api package as they are not using
it directly.
As mentioned above, using the system bundle solves the problem, using the SCR
bundle to track the configuration admin solves the problem as well.
I'm not sure if the current handling RegionConfigurationSupport is really the
way to go. It assumes, that there is a single SCR implementation, but different
CA services per region. However it is also assumed that the CA api package is
shared across the regions. Wouldn't it be easier to remove this stuff and
assume that there is a local SCR service, next to the local CM service?
So it's either both are global or both are distributed across regions, but not
a mixture which might fail due to the above problems anyway.
> 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)
