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

[ https://issues.apache.org/jira/browse/FELIX-5649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16039481#comment-16039481 ] Richard S. Hall commented on FELIX-5649: Ok, I see what you are saying. The reasoning behind not

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

[ https://issues.apache.org/jira/browse/FELIX-5649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16039362#comment-16039362 ] Guillaume Nodet commented on FELIX-5649: See the section 7.4: {code} A fragment bundle will show

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

[ https://issues.apache.org/jira/browse/FELIX-5649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16039347#comment-16039347 ] Guillaume Nodet commented on FELIX-5649: In my case, the fragment is not an extension. But

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

[ https://issues.apache.org/jira/browse/FELIX-5649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16039064#comment-16039064 ] Karl Pauls commented on FELIX-5649: --- Yeah, I'm a bit confused as well. As [~gnodet] references 3.15.1 it

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

[ https://issues.apache.org/jira/browse/FELIX-5649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16039031#comment-16039031 ] Richard S. Hall commented on FELIX-5649: Fragments can have multiple wires, but they should only

Re: Resolver problem causing a fragment to have a wire to the framework ?

>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

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

[ https://issues.apache.org/jira/browse/FELIX-5649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16039010#comment-16039010 ] Guillaume Nodet commented on FELIX-5649: >From the specs (section 3.15.1,

Re: Resolver problem causing a fragment to have a wire to the framework ?

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

Resolver problem...

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

Resolver problem causing a fragment to have a wire to the framework ?

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

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

Guillaume Nodet created FELIX-5649: -- Summary: Refreshing a fragment causes the framework to be restarted Key: FELIX-5649 URL: https://issues.apache.org/jira/browse/FELIX-5649 Project: Felix