[
https://issues.apache.org/jira/browse/FELIX-5507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15868691#comment-15868691
]
David Jencks commented on FELIX-5507:
-------------------------------------
I certainly agree with improving error messages.
It is obviously possible to set up a non-working subsystem by not importing the
system-wide config admin api. However, it's also obviously possible to set up
a non-working subsystem by writing ds components using e.g.
ComponentServiceObjects, including the ds api in the subsystem, and not
importing it. In both these cases, ca and ds apis, I think the appropriate
choices are:
1. import the global apis
2. run (another) ds in the subsystem and turn off global extender.
Are there any plausible use cases that one of these options doesn't cover? Is
there anything useful that you can't do with one of these choices?
IMO if you are using subsystems you have probably already made a fundamental
design mistake and need to accept that you may have to go to some considerable
effort to configure working subsystems. I don't think adding infinite
complexity to try to eliminate every possible way of shooting yourself in the
foot is a reasonable goal.
> ConfigurationAdmin might not be visible to SCR implementation
> -------------------------------------------------------------
>
> 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
> Assignee: 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
> Update: after some discussion, some issues in the framework have been
> identified, but also the SCR implementation is not 100% correct: as it is
> using the bundle context of the extended bundle, it might get a configuration
> admin which interface is not visible to SCR. Therefore it should revert to
> reflection to access the configuration admin.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
