felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Richard S. Hall (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FELIX-5649) Refreshing a fragment causes the framework to be restarted
Date Tue, 06 Jun 2017 19:13:18 GMT

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

Richard S. Hall commented on FELIX-5649:
----------------------------------------

Ok, I see what you are saying. The reasoning behind not letting the ee requirement be hosted
is not clear to me, although I understand there is no need to resolve the ee requirement more
than once for hosting, it does no harm to do it more than once and doesn't create a special
case. But if that is the case, then yes it does seem like refreshing should only consider
host requirements when refreshing fragment dependencies.

> Refreshing a fragment causes the framework to be restarted
> ----------------------------------------------------------
>
>                 Key: FELIX-5649
>                 URL: https://issues.apache.org/jira/browse/FELIX-5649
>             Project: Felix
>          Issue Type: Bug
>    Affects Versions: framework-5.6.2
>            Reporter: Guillaume Nodet
>
> This is caused because the fragment has 2 wires: one to its host and another one to the
system bundle for an osgi.ee requirement.



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

Mime
View raw message