[jira] [Commented] (FELIX-5649) Refreshing a fragment causes the framework to be restarted

["Guillaume Nodet (JIRA)" <ji...@apache.org>]

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

Guillaume Nodet commented on FELIX-5649:
----------------------------------------

From the specs (section 3.15.1, https://github.com/apache/felix/blob/trunk/resolver/src/main/java/org/apache/felix/resolver/ResolverImpl.java#L2027-L2028), it seems that the fact that there are 2 wires on the fragment is expected.
However, such a wire should definitely not cause a refresh of the framework if a fragment is refreshed.
So I'm planning to add an additional test around the following line:
https://github.com/apache/felix/blob/trunk/framework/src/main/java/org/apache/felix/framework/BundleRevisionDependencies.java#L173

{code}
                        if (HostNamespace.HOST_NAMESPACE.equals(bw.getCapability().getNamespace()))
                        {
                            result.add(bw.getProvider().getBundle());
                        }
{code}

> 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)