[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [equinox-dev] Reusing BundleActivator

Oops I retract that statement. That is old SMF behavior not OSGi. If you are using the latest SMF you don't need to do this.

ben

Benjamin Reed wrote:
Yes, the activator must be a local class. To remedy this situation you have to subclass TheActivator and then use that class as your activator:

public class mypack.MyActivator extends common.activator.TheActivator {}

ben

Pascal Rapicault wrote:


Hi,

Is there any restriction in the spec for a bundle to use an activator provided by another bundle.
My case is the following:
Bundle common.activator contains the class *common.activator.TheActivator *and does not have an activator of its own (it's a library)
Bundle foo import commom.activator and has an activator which is *common.activator.TheActivator*


PaScaL