Hi Kevin,
> I was not aware the framework could not wire the package when resolving the
> bundle even if the package is present and exported.
This is true only for optional imports and can occur if the exported package
has an incompatible version, or if a uses constraint prevents the class spac
Tim,
Thanks for the catch. I'm dealing with some third party libs that aren't
OSGi bundles and having to do stuff with declaring things optional and this
one slipped into the mix.
I was not aware the framework could not wire the package when resolving the
bundle even if the package is present an
Hi Kevin,
This problem occurs because you have incorrectly marked the import for the
“com.foo.interfaces” package as “resolution:=optional”. This package is *not*
optional as a type from it is is injected into your blueprint bean which in
turn means that the type must be loadable for your bundl
Hi,
I have a strange problem with class resolution that is befuddling me.
I have a bundle A that uses services from other bundles B and C that
implement an interface I. Bundle A also uses classes from bundle D. I am
using blueprint for bundle A and have a reference-list defined as such:
And
