felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pierre De Rop (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FELIX-5453) Swap callback not called when there are multiple aspects on a service and one of the aspects with lower rank is removed
Date Mon, 19 Dec 2016 13:30:59 GMT

    [ https://issues.apache.org/jira/browse/FELIX-5453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15761165#comment-15761165
] 

Pierre De Rop commented on FELIX-5453:
--------------------------------------

I will investigate but I wonder if you have also the problem with the latest trunk?

> Swap callback not called when there are multiple aspects on a service and one of the
aspects with lower rank is removed
> -----------------------------------------------------------------------------------------------------------------------
>
>                 Key: FELIX-5453
>                 URL: https://issues.apache.org/jira/browse/FELIX-5453
>             Project: Felix
>          Issue Type: Bug
>          Components: Dependency Manager
>    Affects Versions: org.apache.felix.dependencymanager-r8
>            Reporter: Jeroen Daanen
>         Attachments: Activator.java
>
>
> If you have multiple aspects on a service with interface X and one of the aspects with
a lower rank is removed, the service requiring service X does not get the swap callback.
> See the attached Activator with example code.
> The swap method is not called when 'aspect1' is removed.
> Actual output of running the activator:
> {noformat}
> Add: XImpl
> Swap old: XImpl
> Swap new: Aspect1
> Swap old: Aspect1
> Swap new: Aspect2
> Swap old: Aspect2
> Swap new: XImpl
> {noformat}
> I can imagine why swap is not called, because for ServiceRequiringX Aspect1 does not
get really 'swapped' (the service stays Aspect2) But is there any way to find out this is
happening?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message