[
https://issues.apache.org/jira/browse/FELIX-6274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17114149#comment-17114149
]
Timothy James Ward commented on FELIX-6274:
-------------------------------------------
> For your scenario is R6 or R7 log specification being used? or maybe both at
>the same time?
Actually no, our deployment is resolved by bnd and we have two copies of the
log service API at the same version. It happens that sometimes SCR resolves to
a different version from the one used by the other bundles. This triggers the
same failure as in the test. I used R6 and R7 versions in the test to make sure
that the resolver would reliably wire the test bundles to different Log API
class spaces.
The main problem I have is that SCR goes boom when processing my component XML
and never creates my components :)
> Potential Class Space problems with multiple Log Service APIs
> -------------------------------------------------------------
>
> Key: FELIX-6274
> URL: https://issues.apache.org/jira/browse/FELIX-6274
> Project: Felix
> Issue Type: Bug
> Components: Declarative Services (SCR)
> Affects Versions: scr-2.1.20
> Reporter: Timothy James Ward
> Priority: Major
> Fix For: scr-2.1.22
>
>
> The Declarative Services specification requires SCR to inject Logger
> implementations into a DS component (if requested). In order to find a
> suitable Log Service SCR uses its *own* BundleContext, not the context of the
> bundle being extended. This means that if the bundle being extended has a
> different view of the Log Service API then the injection will fail with a
> ClassCastException.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
