Examples of org.osgi.service.framework.CompositeBundle

org.osgi.service.framework.CompositeBundle
Composite bundles are composed of other bundles. The component bundles which make up the content of a composite bundle are installed into a child framework. Like a normal bundle, a composite bundle may import packages and use services from other bundles which are installed in the same framework as the composite bundle. The packages imported and the services used by a composite bundle are shared with the components of a composite bundle through a surrogate bundle installed in the child framework. Also like a normal bundle, a composite bundle may export packages and register services which can be used by bundles installed in the same framework as the composite bundle. The packages exported and the services registered by a composite bundle are acquired from the components of a composite bundle by the surrogate bundle installed in the child framework
A framework has one composite bundle for each of its child frameworks. A framework can have zero or more composite bundles installed. A child framework must have one and only one surrogate bundle which represents the composite bundle in the parent framework. In other words, a parent framework can have many child frameworks but a child framework can have only one parent.
A composite bundle does the following as specified by the composite manifest map:
- Exports packages to the parent framework from the child framework. These packages are imported by the surrogate bundle installed in the child framework.
- Imports packages from the parent framework. These packages are exported by the surrogate bundle installed in the child framework.
- Registers services to the parent framework from the child framework. These services are acquired by the surrogate bundle installed in the child framework.
- Acquires services from the parent framework. These services are registered by the surrogate bundle installed in the child framework.
A newly created child Framework will be in the {@link Bundle#STARTING STARTING} state. This child Framework canthen be used to manage and control the child framework instance. The child framework instance is persistent and uses a storage area associated with the installed composite bundle. The child framework's lifecycle is tied to its composite bundle's lifecycle in the following ways:
- If the composite bundle is marked to be persistently started (see StartLevel.isBundlePersistentlyStarted(Bundle)) then the child framework instance will automatically be started when the composite bundle's start-level is met.
- The child framework instance will be stopped if the composite bundle is persistently stopped or its start level is no longer met. Performing operations which transiently stop a composite bundle do not cause the child framework to stop (e.g. {@link Bundle#stop(int) stop(Bundle.STOP_TRANSIENT)}, {@link Bundle#update() update}, refreshPackages etc.).
- If the composite bundle is uninstalled, the child framework's persistent storage area is also uninstalled.
The child framework may be persistently started and stopped by persistently starting and stopping the composite bundle, but it is still possible to initialize and start the child framework explicitly while the composite bundle is not persistently started. This allows for the child framework to be initialized and populated with a set of bundles before starting the composite bundle. The set of bundles installed into the child framework are the component bundles which comprise the composite bundle.
The child framework's lifecycle is also tied to the lifecycle of its parent framework. When the parent Framework enters the {@link Bundle#STOPPING STOPPING} state, all active child frameworks of thatparent are shutdown using the {@link Framework#stop()} method. The parentframework must not enter the {@link Bundle#RESOLVED} state until all thechild frameworks have completed their shutdown process. Just as with other Bundles, references to child frameworks (or the associated composite and surrogate bundles) become invalid after the parent framework has completed the shutdown process, and must not be allowed to re-initialize or re-start the child framework. @see SurrogateBundle @deprecated This API proposal was rejected by the OSGi Alliance and will not be part of any OSGi specification. Please transition to the org.osgi.framework.hooks API to control resolution, bundle, and service isolation. This API will be removed from Equinox in the 3.9 release You are cautioned against relying upon this API. @ThreadSafe @version $Revision: 6860 $

            compositeManifest.put(Constants.IMPORT_PACKAGE, "org.osgi.service.blueprint;version=\"[1.0.0,2.0.0)\", org.osgi.service.blueprint.container;version=1.0");
            // this export-package is used by pax junit runner as it needs to see the blueprint sample package 
            // for the test after the blueprint sample is started.
            compositeManifest.put(Constants.EXPORT_PACKAGE, "org.apache.aries.blueprint.sample");
            
            CompositeBundle cb = cbf.installCompositeBundle(frameworkConfig, "test-composite", compositeManifest);


            BundleContext compositeBundleContext = cb.getCompositeFramework().getBundleContext();
            // install the blueprint sample onto the framework associated with the composite bundle
            MavenArtifactProvisionOption mapo = mavenBundleInTest("org.apache.aries.blueprint", "org.apache.aries.blueprint.sample");
            // let's use input stream to avoid invoking mvn url handler which isn't avail in the child framework.
            InputStream is = new URL(mapo.getURL()).openStream();
            Bundle bundle = compositeBundleContext.installBundle(mapo.getURL(), is);
            assertNotNull(bundle);
            
            // start the composite bundle then the blueprint sample
            cb.start();
            bundle.start();


            // do the test
            testBlueprintContainer(compositeBundleContext, bundle);

View Full Code Here

        }
    }
        
     private void openTracker(Bundle b, String bundleScope, int stateMask) {
         // let's process each of the bundle in the CompositeBundle
         CompositeBundle cb = (CompositeBundle) b;
         BundleContext compositeBundleContext = cb
                 .getCompositeFramework().getBundleContext();


         // let's track each of the bundle in the CompositeBundle
         BundleTracker bt = new BundleTracker(compositeBundleContext,
                 stateMask, this);

View Full Code Here

0 1 2

TOP

Related Classes of org.osgi.service.framework.CompositeBundle

org.apache.aries.application.runtime.framework.BundleFrameworkFactoryImpl

org.apache.aries.blueprint.itests.BlueprintContainer2BTCustomizerTest

org.apache.aries.blueprint.itests.BlueprintContainerBTCustomizerTest

org.apache.aries.util.RecursiveBundleTrackerTest

org.apache.aries.util.tracker.AbstractBundleTrackerCustomizer

org.apache.aries.util.tracker.AriesBundleTrackerCustomizer

org.apache.aries.util.tracker.InternalRecursiveBundleTracker

org.eclipse.osgi.internal.composite.CompositeConfigurator

All source code are property of their respective owners. Java is a trademark of Sun Microsystems, Inc and owned by ORACLE Inc. Contact coftware#gmail.com.