I think the intention was that if you can not resolve, you can not
return the required resources. I think returning null in this case (or
maybe even IllegalStateException?) makes sense. When you are not
resolved, the required resources are undefined.
My (too long) action list states I have to make an update for RFC 112.
Any more of those issues are highly appreciated.
Kind regards,
Peter Kriens
On 24 jun 2008, at 22:29, David Albert wrote:
Hey All,
This is somewhat related to the question I had last Thursday. There
is scant info in the OBR spec on what getRequiredResources() does
besides return an array of Resources. When we can resolve, it makes
sense for getRequiredResources() to return every Resource we need to
install in order to install the Resources the user has specified,
but if we cannot resolve, I am at a loss for what
getRequiredResources() should return. It would seem that there is
no useful way to return a list of all the required resources if we
can't satisfy all of them with the info in our repository. Is there
a generally accepted way of doing this? Perhaps returning null if
we can't resolve, an empty array if we can resolve but there are no
dependencies, and an array of required resoruces otherwise?
Also, if I have manually added two bundles to my resovler, Foo and
Bar, where Foo imports a package exported by Bar, would Bar be added
to required resources? I would say no, considering that the user
has already said he is going to install it and required resources
seems to be for packages that we need to install to do what the user
wants. Thoughts?
Thanks,
-D
--
David Albert
Bug Labs
_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev
