More Bundle Activator Osgi images. Bundle-Description: A description of the bundle's functionality. Bundle-ManifestVersion: Indicates the OSGi specification to use for reading this bundle. Bundle-Version: Designates a version number to the bundle. Pretty Ricky Bluestars 2 Rar. Bundle-Activator: Indicates the class name to be invoked once a bundle is activated.

Refine your search by using the following advanced search options. Criteria Usage Questions with keyword1 or keyword2 keyword1 keyword2 Questions with a mandatory word, e.g. Keyword2 keyword1 +keyword2 Questions excluding a word, e.g. Keyword2 keyword1 -keyword2 Questions with keyword(s) and a specific tag keyword1 [tag1] Questions with keyword(s) and either of two or more specific tags keyword1 [tag1] [tag2] To search for all posts by a user or all posts with a specific tag, start typing and choose from the suggestion list. Do not use a plus or minus sign with a tag, e.g., +[tag1]. I am having an issue now with regards to the starting up of an OSGi bundle in Liberty as the Activator.start() does not seem to get called. It has a space there.

As usual, the logs still says (as below) without any print-outs from the Activator start up: [5/25/15 8:44:59:956 GMT] 00000026 com.ibm.ws.app.manager.AppMessageHelper I CWWKZ0018I: Starting application address-1.0.11. Alcohol 52 1.9.8.7612 Free. [5/25/15 8:45:00:853 GMT] 00000026 com.ibm.ws.app.manager.AppMessageHelper A CWWKZ0001I: Application address-1.0.11 started in 0.898 seconds. I thought perhaps the class in 'coreweb.resource' is missing in the bundle thus the bundle could not be resolved.

So I have added classes within 'coreweb.resource' into the jar file of the bundle but still that made no difference. The logs still appears as above. Babok 3.0. Note that I am running on Liberty on CICS 5.2.

I have resolved this. It is because the 'Import-Package' in the manifest file is incomplete. After manually going through all the imports dependencies and adding in the additional import packages and wire them with a corresponding jar file in the bundle, it now deploys fine and the Activator gets called as expected. It is unfortunate however that no errors were thrown when the 'Import-Package' were incomplete. I would have thought the bundle resolution step would at least have thrown some errors.