You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Karl Pauls (JIRA)" <ji...@apache.org> on 2017/02/14 16:19:42 UTC

[jira] [Resolved] (FELIX-5544) Don't take implicit boot delegation into account on service assignability check

     [ https://issues.apache.org/jira/browse/FELIX-5544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Karl Pauls resolved FELIX-5544.
-------------------------------
    Resolution: Fixed

I fixed this in r1782982. I added a test case that reproduces the issue and makes sure its working as well as makes sure the implicitbootdelegation is working for the normal class load.

> Don't take implicit boot delegation into account on service assignability check
> -------------------------------------------------------------------------------
>
>                 Key: FELIX-5544
>                 URL: https://issues.apache.org/jira/browse/FELIX-5544
>             Project: Felix
>          Issue Type: Bug
>          Components: Framework
>    Affects Versions: framework-5.6.1
>            Reporter: Karl Pauls
>            Assignee: Karl Pauls
>             Fix For: framework-5.6.2
>
>
> We have a problem in the service lookup path when,
> 1) the class that instigates the lookup is coming from the outside
> 2) and the service class can actually be loaded from the outside but isn’t assignable to the class of the service
> 3) and both, the requirer and the provider, don’t have a wire to the package of the service class.
> We need to stop trying to implicitly bootdelegate in the service lookup.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)