Hi Roshan.
We're using the OBR bundle outside of an OSGi gateway (as a simple
library), so having the OBR tightly coupled with a BundleContext
instance will break our software.
What I'm more in favor for is to be able to use the BundleContext *when
there is one available*, but do not make it mandatory.
Regards
--Guillaume
Roshan A. Punnoose wrote:
Hi,
Looking into the OBR code, I think it might be useful to have the OBR
RepositoryAdmin tied to the BundleContext and the bundles that are
already active in OSGi container. Right now, I am running the felix OBR
bundle in Equinox, but it does not tie to the BundleContext. So when I
try and add an OBR repository xml containing plugins that already exist
in the container, it throws an exception because these bundles already
exist in the container. However, if the OBR bundle was tied to the
BundleContext, it should see that there are already Resources/Bundles
available to the container and not try and deploy these.
I can see where to do it in the code, and I can submit a patch for it.
Is this a path that seems reasonable to you?
Roshan
