Java Reference
In-Depth Information
Table A.1
OSGi manifest headers
(continued)
Header
Attributes and directives
Comments
See sections 5.1.2 and
7.2.1.
Import-Package
bundle-symbolic-name
bundle-version
resolution
specification-version
version
Deprecated.
Import-Service
InitialProvisioning-Entries
See chapter 3.
Meta-Persistence
Provide-Capability
effective:1
uses
See chapter 7.
See section 10.4.2 .
Remote-Service
Require-Bundle
bundle-version
resolution
visibility
See section 5.1.2.
See chapter 7.
Require-Capability
effective:1
filter
resolve
See section 10.6.
SCA-Configuration
Path to declarative ser-
vices metadata files.
Wildcards may be used.
See section 6.2.3.
Service-Component
See section 2.2.1.
Web-ContextPath
A.3.2
The bundle context
Every active bundle has a bundle context. The bundle context acts as an intermediary
between the bundle and the outside framework. The bundle context can be used to
programmatically install new bundles and query the existing bundles. It can also be
used for more advanced functions, such as requesting persistent storage areas, sub-
scribing to events, registering services, and retrieving services.
A.3.3
Dependency management
One of the main functions of
OSG
i bundles is to allow dependencies to be explicitly
declared and resolved. Resolving is an import concept, and we discussed it in depth in
chapter 7. Resolving is the process by which the
OSG
i framework determines whether
bundles have all of their required package imports, and which bundles should supply
these package imports. (It's the absence of resolving in standard Java that results in
