Resolver problem?

2010-03-29 Thread David Jencks
I just saw this... I'm pretty sure its from org.apache.felix.framework-2.1.0-20100325.084125-18.jar java.lang.ArrayIndexOutOfBoundsException: -1 at java.util.ArrayList.get(ArrayList.java:324) at org.apache.felix.framework.resolver.ResolverImpl$Blame.toString(ResolverImpl.java:1

Resolver problem...

2017-06-06 Thread Guillaume Nodet
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

Re: Resolver problem?

2010-03-31 Thread Richard S. Hall
Thanks for reporting it, I will look into it. -> richard On 3/30/10 5:39, David Jencks wrote: I just saw this... I'm pretty sure its from org.apache.felix.framework-2.1.0-20100325.084125-18.jar java.lang.ArrayIndexOutOfBoundsException: -1 at java.util.ArrayList.get(ArrayList.java:3

Re: Resolver problem?

2010-03-31 Thread Richard S. Hall
We needed to check for an empty list before grabbing an element from it...I committed a fix and deployed a new snapshot... -> richard On 3/29/10 17:39, David Jencks wrote: I just saw this... I'm pretty sure its from org.apache.felix.framework-2.1.0-20100325.084125-18.jar java.lang.ArrayInd

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

2017-06-06 Thread Guillaume Nodet
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

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

2017-06-06 Thread Guillaume Nodet
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

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

2017-06-06 Thread Guillaume Nodet
>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