[
https://issues.apache.org/jira/browse/FELIX-5507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15838480#comment-15838480
]
David Jencks commented on FELIX-5507:
-------------------------------------
As of Sept 2016 IBM Websphere Liberty was using the single SCR/mutliple CA
support, so removing it might result in some pushback. As of that time I
wasn't aware of any problems with it.
You can run with local SCR services by setting the global extender property to
false.
I couldn't figure out any way to have isolated CA API. It doesn't appear to be
a problem (judging by Liberty) to share the API and not share the service
implementation.
Do you understand why your setup doesn't work? I don't. I suspect a bug
outside SCR.
> 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)
