Build 132 of
Netigso is pretty cool—an OSGi
BundleActivator is created when you use the Module Installer wizard in an OSGI Bundle project:
- Create OSGi Bundle project:
- Specify location and whether it belongs to an application:
- Specify unique code name, display name, localizing bundle, and optional layer.xml file:
- Finish the wizard and then you have the applicable OSGi keys in your manifest, as well as a dependency on the OSGi framework, so that you can reference the OSGi container APIs (that's thanks to Build 131 of Netigso):
- Next, use the "Module Installer" wizard, exactly as you'd do for a NetBeans module. I.e., nothing to fill in at all, simply click Finish:
- And now you have a BundleActivator class, instead of a NetBeans API ModuleInstall class:
Excellent, right? Now, the main thing I'm looking forward to is services in BundleContexts being added to the Lookup of applications, so that NetBeans modules can use the Lookup to access those OSGi services!
Hi Geertjan, are your BundleActivators getting called? Mine seem to be ignored... (build 142)
--Toni
Sorry it's build 143
What do you see in the Manifest? You should see the BundleActivator registered there.
The Manifest is ok, the Problem is that either the output to system.out in the my bundleactivator is ignored, or start isn't called...
Works for me! Why don't you create a bundle, then send it to me, and I will integrate it into my application and then I will describe how to do so?