Docjar: A Java Source and Docuemnt Enginecom.*    java.*    javax.*    org.*    all    new    plug-in

Quick Search    Search Deep

org.osgi.framework.* (21)org.osgi.service.* (63)org.osgi.util.* (7)

Package Samples:

org.osgi.service.prefs
org.osgi.util.tracker
org.osgi.service.url
org.osgi.service.startlevel
org.osgi.service.permissionadmin
org.osgi.service.packageadmin
org.osgi.framework
org.osgi.util.xml
org.osgi.util.measurement
org.osgi.util.position
org.osgi.service.wireadmin
org.osgi.service.useradmin
org.osgi.service.upnp
org.osgi.service.provisioning
org.osgi.service.device
org.osgi.service.cm
org.osgi.service.http
org.osgi.service.io
org.osgi.service.jini
org.osgi.service.log

Classes:

Preferences: A node in a hierarchical collection of preference data. This interface allows applications to store and retrieve user and system preference data. This data is stored persistently in an implementation-dependent backing store. Typical implementations include flat files, OS-specific registries, directory servers and SQL databases. For each bundle, there is a separate tree of nodes for each user, and one for system preferences. The precise description of "user" and "system" will vary from one bundle to another. Typical information stored in the user preference tree might include font choice, and color ...
ConfigurationAdmin: Service for administering configuration data. The main purpose of this interface is to store bundle configuration data persistently. This information is represented in Configuration objects. The actual configuration data is a Dictionary of properties inside a Configuration object. There are two principally different ways to manage configurations. First there is the concept of a Managed Service, where configuration data is uniquely associated with an object registered with the service registry. Next, there is the concept of a factory where the Configuration Admin service will maintain 0 or more ...
UserAdminPermission: Permission to configure and access the Role objects managed by a User Admin service. This class represents access to the Role objects managed by a User Admin service and their properties and credentials (in the case of User objects). The permission name is the name (or name prefix) of a property or credential. The naming convention follows the hierarchical property naming convention. Also, an asterisk may appear at the end of the name, following a ".", or by itself, to signify a wildcard match. For example: "org.osgi.security.protocol.*" or "*" is valid, but "*protocol" ...
Producer: Data Producer, a service that can generate values to be used by Consumer services. Service objects registered under the Producer interface are expected to produce values (internally generated or from external sensors). The value can be of different types. When delivering a value to a Wire object, the Producer service should coerce the value to be an instance of one of the types specified by Wire.getFlavors() 55 . The classes are specified in order of preference. When the data represented by the Producer object changes, this object should send the updated value by calling the update method on each ...
ManagedService: A service that can receive configuration data from a Configuration Admin service. A Managed Service is a service that needs configuration data. Such an object should be registered with the Framework registry with the service.pid property set to some unique identitifier called a PID. If the Configuration Admin service has a Configuration object corresponding to this PID, it will callback the updated() method of the ManagedService object, passing the properties of that Configuration object. If it has no such Configuration object, then it calls back with a null properties argument. Registering a Managed ...
ManagedServiceFactory: Manage multiple service instances. Bundles registering this interface are giving the Configuration Admin service the ability to create and configure a number of instances of a service that the implementing bundle can provide. For example, a bundle implementing a DHCP server could be instantiated multiple times for different interfaces using a factory. Each of these service instances is represented, in the persistent storage of the Configuration Admin service, by a factory Configuration object that has a PID. When such a Configuration is updated, the Configuration Admin service calls the ManagedServiceFactory ...
XMLParserActivator: A BundleActivator class that allows any JAXP compliant XML Parser to register itself as an OSGi parser service. Multiple JAXP compliant parsers can concurrently register by using this BundleActivator class. Bundles who wish to use an XML parser can then use the framework's service registry to locate available XML Parsers with the desired characteristics such as validating and namespace-aware. The services that this bundle activator enables a bundle to provide are: javax.xml.parsers.SAXParserFactory ( SAXFACTORYNAME 55 ) javax.xml.parsers.DocumentBuilderFactory ( DOMFACTORYNAME 55 ) The algorithm ...
Group: A named grouping of roles ( Role objects). Whether or not a given Authorization context implies a Group object depends on the members of that Group object. A Group object can have two kinds of members: basic and required . A Group object is implied by an Authorization context if all of its required members are implied and at least one of its basic members is implied. A Group object must contain at least one basic member in order to be implied. In other words, a Group object without any basic member roles is never implied by any Authorization context. A User object always implies itself. No loop ...
ConfigurationPlugin: A service interface for processing configuration dictionary before the update. A bundle registers a ConfigurationPlugin object in order to process configuration updates before they reach the Managed Service or Managed Service Factory. The Configuration Admin service will detect registrations of Configuration Plugin services and must call these services every time before it calls the ManagedService or ManagedServiceFactory updated method. The Configuration Plugin service thus has the opportunity to view and modify the properties before they are passed to the ManagedS ervice or Managed Service Factory. ...
BundleContext: A bundle's execution context within the Framework. The context is used to grant access to other methods so that this bundle can interact with the Framework. BundleContext methods allow a bundle to: Subscribe to events published by the Framework. Register service objects with the Framework service registry. Retrieve ServiceReferences from the Framework service registry. Get and release service objects for a referenced service. Install new bundles in the Framework. Get the list of bundles installed in the Framework. Get the Bundle object for a bundle. Create File objects for files in a persistent ...
Configuration: The configuration information for a ManagedService or ManagedServiceFactory object. The Configuration Admin service uses this interface to represent the configuration information for a ManagedService or for a service instance of a ManagedServiceFactory . A Configuration object contains a configuration dictionary and allows the properties to be updated via this object. Bundles wishing to receive configuration dictionaries do not need to use this class - they register a ManagedService or ManagedServiceFactory . Only administrative bundles, and bundles wishing to update their own configurations need ...
Consumer: Data Consumer, a service that can receive udpated values from Producer services. Service objects registered under the Consumer interface are expected to consume values from a Producer service via a Wire object. A Consumer service may poll the Producer service by calling the Wire.poll() 55 method. The Consumer service will also receive an updated value when called at it's updated(org.osgi.service.wireadmin.Wire, java.lang.Object) 55 method. The Producer service should have coerced the value to be an instance of one of the types specified by the Wire.getFlavors() 55 method, or one of their subclasses. ...
ProvisioningService: Service for managing the initial provisioning information. Initial provisioning of an OSGi device is a multi step process that culminates with the installation and execution of the initial management agent. At each step of the process, information is collected for the next step. Multiple bundles may be involved and this service provides a means for these bundles to exchange information. It also provides a means for the initial Management Bundle to get its initial configuration information. The provisioning information is collected in a Dictionary object, called the Provisioning Dictionary. Any ...
Authorization: The Authorization interface encapsulates an authorization context on which bundles can base authorization decisions, where appropriate. Bundles associate the privilege to access restricted resources or operations with roles. Before granting access to a restricted resource or operation, a bundle will check if the Authorization object passed to it possess the required role, by calling its hasRole method. Authorization contexts are instantiated by calling the UserAdmin.getAuthorization(org.osgi.service.useradmin.User) 55 method. Trusting Authorization objects There are no restrictions regarding the ...
WireAdminEvent: A Wire Admin Event. WireAdminEvent objects are delivered asynchronously to all registered WireAdminListener service objects which specify an interest in the WireAdminEvent type. However, events must be delivered in chronological order with respect to each listener. For example, a WireAdminEvent of type WIRE_CONNECTED 55 must be delivered before a WireAdminEvent of type WIRE_DISCONNECTED 55 for a particular Wire object. A type code is used to identify the type of event. The following event types are defined: WIRE_CREATED 55 WIRE_CONNECTED 55 WIRE_UPDATED 55 WIRE_TRACE 55 WIRE_DISCONNECTED 55 WIRE_DELETED ...
StartLevel: The StartLevel service allows management agents to manage a start level assigned to each bundle and the active start level of the Framework. There is at most one StartLevel service present in the OSGi environment. A start level is defined to be a state of execution in which the Framework exists. StartLevel values are defined as unsigned integers with 0 (zero) being the state where the Framework is not launched. Progressively higher integral values represent progressively higher start levels. e.g. 2 is a higher start level than 1. Access to the StartLevel service is protected by corresponding ServicePermission ...
Wire: A connection between a Producer service and a Consumer service. A Wire object connects a Producer service to a Consumer service. Both the Producer and Consumer services are identified by their unique service.pid values. The Producer and Consumer services may communicate with each other via Wire objects that connect them. The Producer service may send updated values to the Consumer service by calling the update(java.lang.Object) 55 method. The Consumer service may request an updated value from the Producer service by calling the poll() 55 method. A Producer service and a Consumer service may be ...
Bundle: An installed bundle in the Framework. A Bundle object is the access point to define the life cycle of an installed bundle. Each bundle installed in the OSGi environment will have an associated Bundle object. A bundle will have a unique identity, a long , chosen by the Framework. This identity will not change during the life cycle of a bundle, even when the bundle is updated. Uninstalling and then reinstalling the bundle will create a new unique identity. A bundle can be in one of six states: UNINSTALLED 55 INSTALLED 55 RESOLVED 55 STARTING 55 STOPPING 55 ACTIVE 55 Values assigned to these states ...
PermissionAdmin: The Permission Admin service allows management agents to manage the permissions of bundles. There is at most one Permission Admin service present in the OSGi environment. Access to the Permission Admin service is protected by corresponding ServicePermission . In addition AdminPermission is required to actually set permissions. Bundle permissions are managed using a permission table. A bundle's location serves as the key into this permission table. The value of a table entry is the set of permissions (of type PermissionInfo ) granted to the bundle named by the given location. A bundle may have an ...
WireAdminListener: Listener for Wire Admin Events. WireAdminListener objects are registered with the Framework service registry and are notified with a WireAdminEvent object when an event is broadcast. WireAdminListener objects can inspect the received WireAdminEvent object to determine its type, the Wire object with which it is associated, and the Wire Admin service that broadcasts the event. WireAdminListener objects must be registered with a service property WireConstants.WIREADMIN_EVENTS 55 whose value is a bitwise OR of all the event types the listener is interested in receiving. For example: Integer mask = ...
UPnPEventListener: UPnP Events are mapped and delivered to applications according to the OSGi whiteboard model. An application that wishes to be notified of events generated by a particular UPnP Device registers a service extending this interface. The notification call from the UPnP Service to any UPnPEventListener object must be done asynchronous with respect to the originator (in a separate thread). Upon registration of the UPnP Event Listener service with the Framework, the service is notified for each variable which it listens for with an initial event containing the current value of the variable. Subsequent ...
Envelope: Identifies a contained value. An Envelope object combines a status value, an identification object and a scope name. The Envelope object allows the use of standard Java types when a Producer service can produce more than one kind of object. The Envelope object allows the Consumer service to recognize the kind of object that is received. For example, a door lock could be represented by a Boolean object. If the Producer service would send such a Boolean object, then the Consumer service would not know what door the Boolean object represented. The Envelope object contains an identification object ...
Role: The base interface for Role objects managed by the User Admin service. This interface exposes the characteristics shared by all Role classes: a name, a type, and a set of properties. Properties represent public information about the Role object that can be read by anyone. Specific UserAdminPermission objects are required to change a Role object's properties. Role object properties are Dictionary objects. Changes to these objects are propagated to the User Admin service and made persistent. Every User Admin service contains a set of predefined Role objects that are always present and cannot be removed. ...
UserAdmin: This interface is used to manage a database of named Role objects, which can be used for authentication and authorization purposes. This version of the User Admin service defines two types of Role objects: "User" and "Group". Each type of role is represented by an int constant and an interface. The range of positive integers is reserved for new types of roles that may be added in the future. When defining proprietary role types, negative constant values must be used. Every role has a name and a type. A User object can be configured with credentials (e.g., a password) and properties (e.g., a street ...
Measurement: Represents a value with an error, a unit and a time-stamp. A Measurement object is used for maintaining the tuple of value, error, unit and time-stamp. The value and error are represented as doubles and the time is measured in milliseconds since midnight, January 1, 1970 UTC. Mathematic methods are provided that correctly calculate taking the error into account. A runtime error will occur when two measurements are used in an incompatible way. E.g., when a speed (m/s) is added to a distance (m). The measurement class will correctly track changes in unit during multiplication and division, always ...

Home | Contact Us | Privacy Policy | Terms of Service