Start line:  
End line:  

Snippet Preview

Snippet HTML Code

Stack Overflow Questions
  /*
   * Copyright (c) OSGi Alliance (2010, 2011). All Rights Reserved.
   * 
   * Licensed under the Apache License, Version 2.0 (the "License");
   * you may not use this file except in compliance with the License.
   * You may obtain a copy of the License at
   *
   *      http://www.apache.org/licenses/LICENSE-2.0
   *
  * Unless required by applicable law or agreed to in writing, software
  * distributed under the License is distributed on an "AS IS" BASIS,
  * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
  * See the License for the specific language governing permissions and
  * limitations under the License.
  */
 
 package org.osgi.framework.wiring;
 
 import java.util.List;
 
Bundle Revision. When a bundle is installed and each time a bundle is updated, a new bundle revision of the bundle is created. Since a bundle update can change the entries in a bundle, different bundle wirings for the same bundle can be associated with different bundle revisions.

For a bundle that has not been uninstalled, the most recent bundle revision is defined to be the current bundle revision. A bundle in the UNINSTALLED state does not have a current revision. The current bundle revision for a bundle can be obtained by calling bundle.adapt (BundleRevision.class). Since a bundle in the UNINSTALLED state does not have a current revision, adapting such a bundle returns null.

The framework defines name spaces for package, bundle and host capabilities and requirements. These name spaces are defined only to express wiring information by the framework. They must not be used in Provide-Capability and Require-Capability manifest headers.

Version:
$Id: 139b3046ebd46c48b03dda8d36f2f9d79e2e616d $
ThreadSafe:
Noimplement:
 
 public interface BundleRevision extends BundleReference {
Returns the symbolic name for this bundle revision.

Returns:
The symbolic name for this bundle revision.
See also:
org.osgi.framework.Bundle.getSymbolicName()
 
Returns the version for this bundle revision.

Returns:
The version for this bundle revision, or org.osgi.framework.Version.emptyVersion if this bundle revision has no version information.
See also:
org.osgi.framework.Bundle.getVersion()
 
Returns the capabilities declared by this bundle revision.

Parameters:
namespace The name space of the declared capabilities to return or null to return the declared capabilities from all name spaces.
Returns:
A list containing a snapshot of the declared BundleCapabilitys, or an empty list if this bundle revision declares no capabilities in the specified name space. The list contains the declared capabilities in the order they are specified in the manifest.
 
Returns the requirements declared by this bundle revision.

Parameters:
namespace The name space of the declared requirements to return or null to return the declared requirements from all name spaces.
Returns:
A list containing a snapshot of the declared BundleRequirements, or an empty list if this bundle revision declares no requirements in the specified name space. The list contains the declared requirements in the order they are specified in the manifest.
 
Name space for package capabilities and requirements.

The name of the package is stored in the capability attribute of the same name as this name space (osgi.wiring.package). The other directives and attributes of the package, from the Export-Package manifest header, can be found in the cabability's directives and attributes. The version capability attribute must contain the org.osgi.framework.Version of the package if one is specified or org.osgi.framework.Version.emptyVersion if not specified. The bundle-symbolic-name capability attribute must contain the symbolic name of the provider if one is specified. The bundle-version capability attribute must contain the version of the provider if one is specified or org.osgi.framework.Version.emptyVersion if not specified.

The package capabilities provided by the system bundle, that is the bundle with id zero, must include the package specified by the org.osgi.framework.Constants.FRAMEWORK_SYSTEMPACKAGES and org.osgi.framework.Constants.FRAMEWORK_SYSTEMPACKAGES_EXTRA framework properties as well as any other package exported by the framework implementation.

A bundle revision declares zero or more package capabilities (this is, exported packages) and declares zero or more package requirements.

A bundle wiring provides zero or more resolved package capabilities (that is, exported packages) and requires zero or more resolved package requirements (that is, imported packages). The number of package wires required by a bundle wiring may change as the bundle wiring may dynamically import additional packages.

	String	PACKAGE_NAMESPACE"osgi.wiring.package";

Name space for bundle capabilities and requirements.

The bundle symbolic name of the bundle is stored in the capability attribute of the same name as this name space (osgi.wiring.bundle). The other directives and attributes of the bundle, from the Bundle-SymbolicName manifest header, can be found in the cabability's directives and attributes. The bundle-version capability attribute must contain the org.osgi.framework.Version of the bundle from the Bundle-Version manifest header if one is specified or org.osgi.framework.Version.emptyVersion if not specified.

A non-fragment revision declares exactly one bundle capability (that is, the bundle can be required by another bundle). A fragment revision must not declare a bundle capability.

A bundle wiring for a non-fragment revision provides exactly one bundle capability (that is, the bundle can be required by another bundle) and requires zero or more bundle capabilities (that is, requires other bundles).

† A bundle with no bundle symbolic name (that is, a bundle with Bundle-ManifestVersion < 2) must not provide a bundle capability.

	String	BUNDLE_NAMESPACE"osgi.wiring.bundle";

Name space for host capabilities and requirements.

The bundle symbolic name of the bundle is stored in the capability attribute of the same name as this name space (osgi.wiring.host). The other directives and attributes of the bundle, from the Bundle-SymbolicName manifest header, can be found in the cabability's directives and attributes. The bundle-version capability attribute must contain the org.osgi.framework.Version of the bundle from the Bundle-Version manifest header if one is specified or org.osgi.framework.Version.emptyVersion if not specified.

A non-fragment revision declares zero or one host capability if the bundle allows fragments to be attached. A fragment revision must declare exactly one host requirement.

A bundle wiring for a non-fragment revision provides zero or one host capability if the bundle allows fragments to be attached. A bundle wiring for a fragment revision requires a host capability for each host to which it is attached.

† A bundle with no bundle symbolic name (that is, a bundle with Bundle-ManifestVersion < 2) must not provide a host capability.

	String	HOST_NAMESPACE"osgi.wiring.host";

Returns the special types of this bundle revision. The bundle revision type values are: A bundle revision may be more than one type at a time. A type code is used to identify the bundle revision type for future extendability.

If this bundle revision is not one or more of the defined types then 0 is returned.

Returns:
The special types of this bundle revision. The type values are ORed together.
	int getTypes();

Bundle revision type indicating the bundle revision is a fragment.

See also:
getTypes()
	int	TYPE_FRAGMENT	= 0x00000001;

Returns the bundle wiring which is using this bundle revision.

Returns:
The bundle wiring which is using this bundle revision or null if no bundle wiring is using this bundle revision.
See also:
BundleWiring.getRevision()
New to GrepCode? Check out our FAQ X