I just hit a problem where refreshing a fragment cause the framework to
be wrongly refreshed.
This is caused by the fragment's wiring having 2 wires: one to its host,
and another one for an osgi.ee requirement.
My understanding is that fragments should only be wired to their hosts.
This is a regres
Actually, the bug (if it's a bug) is much older, as I can observe the same
behavior with framework 5.0.0.
I can't easily try with 4.x lines though...
2017-06-06 15:47 GMT+02:00 Guillaume Nodet :
> I just hit a problem where refreshing a fragment cause the framework to
> be wrongly refreshed.
> Th
>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 f
