Re: Issue with BundleListener/Resolved events

Ok, thank you ! For now I will implement the ordering on my side, inside the listener, as it will be required to work on all frameworks .. If I really need it I will open an RFE and try to provide a patch for that. Regards Thomas On Wed, Jan 13, 2016 at 4:25 PM Richard S. Hall

Re: Issue with BundleListener/Resolved events

Hi, It's not about classes (which are correctly loaded by the framework and fully available when i get in there), but about custom resources/capabilities that I register in the listener. So yes, it fails, as the listener cannot load the resources it depends on, which should have been registered

Issue with BundleListener/Resolved events

Hi there, I have an issue when listening to resolved event - my BundleListener actually doesn't receive the events in the correct order, where the bundle resolution really happened. Let's say we have bundle X , which has a Import-Package: org.aPackage , and a bundle Y , which Export-Package:

Re: Issue with BundleListener/Resolved events

On 1/12/16 11:59 , Thomas Draier wrote: On Tue, Jan 12, 2016 at 5:45 PM Richard S. Hall wrote: So, are you saying that when you get a resolved event for some arbitrary bundle, you are running into issues because some of its dependencies are not yet treated as if they

Re: Issue with BundleListener/Resolved events

I think you may be reading more into the spec than what is there. Technically, a resolve is atomic so all bundles are effectively resolved at the same time, which means the events occur at the same time, but since we can only deliver one at a time, then you receive them in some arbitrary order

Re: Issue with BundleListener/Resolved events

On Tue, Jan 12, 2016 at 5:45 PM Richard S. Hall wrote: > > So, are you saying that when you get a resolved event for some arbitrary > bundle, you are running into issues because some of its dependencies are > not yet treated as if they are resolved? What is the symptom you

Re: Issue with BundleListener/Resolved events

Hi Richard, Thank you for your answer. I'll try to clarify my needs : I actually have a listener which listen to all bundles resolution. This listener register resources, which have dependencies to other resources from other bundles. Resource registration just cannot happen if dependent resources