Issue 53 in peaberry: PeaberryActivationModule should provide a reference to OSGi BundleContext

[peab...@googlecode.com]

Status: New
Owner: ----
Labels: Type-Enhancement Priority-Medium

New issue 53 by yungkce: PeaberryActivationModule should provide a
reference to OSGi BundleContext
http://code.google.com/p/peaberry/issues/detail?id=53

If the user uses the automatic bootstrapping of Peaberry bundles, there is
NO way to get the BundleContext object.

[Todor Boev]

The BundleContext intance of your bundle is bound into Guice. You
should be able to simply inject it where needed.

> --
> You received this message because you are subscribed to the Google Groups
> "Guice and OSGi" group.
> To post to this group, send email to guice...@googlegroups.com.
> To unsubscribe from this group, send email to
> guice-osgi+...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/guice-osgi?hl=en.
>
>

[peab...@googlecode.com]

Comment #1 on issue 53 by mcculls: PeaberryActivationModule should provide

a reference to OSGi BundleContext
http://code.google.com/p/peaberry/issues/detail?id=53

As Todor mentioned on the mailing list, just @Inject BundleContext wherever
you need it.

[peab...@googlecode.com]

Comment #2 on issue 53 by yungkce: PeaberryActivationModule should provide

a reference to OSGi BundleContext
http://code.google.com/p/peaberry/issues/detail?id=53

But what if I would like to refer to the BundleContext in the
PeaberryActivationModule's configure() method? It is before Guice @Inject
the BundleContext object.

[peab...@googlecode.com]

Comment #3 on issue 53 by mcculls: PeaberryActivationModule should provide

a reference to OSGi BundleContext
http://code.google.com/p/peaberry/issues/detail?id=53

Can you elaborate on what you need to use the BundleContext for in the
module itself? Binding modules are usually small and side-effect free, so
I'm just wondering why you need the context when setting up bindings.

[peab...@googlecode.com]

Comment #4 on issue 53 by yungkce: PeaberryActivationModule should provide

a reference to OSGi BundleContext
http://code.google.com/p/peaberry/issues/detail?id=53

Since I would like to use the Manifest header of the bundle for setting the
attributes of the exported services inside the configure() method, the only
way to get those header is from the BundleContext.getBundle().getHeaders()
method unless I can export the services outside the configure() method.

[peab...@googlecode.com]

Comment #5 on issue 53 by Rinsvind: PeaberryActivationModule should provide

a reference to OSGi BundleContext
http://code.google.com/p/peaberry/issues/detail?id=53

It seems best to pass the BundleContext to the module constructor.
Currently we expect the module to have a default constructor. We could
support a constructor with a BundleContext as well. I am not sure how nice
this will be since now there are two ways to obtain the BundleContext and
the users cat try to bind it a second time.

Stuart what do you think?

[peab...@googlecode.com]

Updates:
Labels: Peaberry-Extension

Comment #6 on issue 53 by mccu...@gmail.com: PeaberryActivationModule

should provide a reference to OSGi BundleContext
http://code.google.com/p/peaberry/issues/detail?id=53

(No comment was entered for this change.)

[peab...@googlecode.com]

Updates:
Status: Duplicate

Comment #7 on issue 53 by mccu...@gmail.com: PeaberryActivationModule

should provide a reference to OSGi BundleContext

https://code.google.com/p/peaberry/issues/detail?id=53

Moved to https://github.com/ops4j/peaberry/issues/56

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings