Declarative Services Specification - The Declarative Services specification provides dependency injection for services. It handles the service life cycle dynamics by notifying the component or managing the component's life cycle. See chapter Declarative Services Specification.

CDI Integration Specification - The CDI Integration Specification describes how OSGi is integrated into the CDI programming model, allowing developer to leverage CDI annotations, injection and extensions with OSGi bundles and services. See chapter CDI Integration Specification.

Remote Services - The Remote Services specification defines a number of service properties that participating bundles can use to convey information to a distribution provider. The distribution provider creates endpoints that are accessible to remote clients or registers proxies that access services hosted external to the OSGi framework. See chapter Remote Services.

Remote Service Admin Service Specification - The Remote Services Admin Service Specification defines an API for the distribution provider and discovery of services in a network. A management agent can use this API to provide an actual distribution policy. This management agent can export and import services as well as discovering services in the network. See Remote Service Admin Service Specification.

Cluster Information Specification - This specification defines services that facilitate the discovery, introspection and management of a cluster of nodes in a networked environment. This applies to Cloud environments as well as Embedded and IoT use cases where multiple nodes are exist that need to be orchestrated into performing a coordinated set of functionalities. See Cluster Information Specification.

JAX-RS Whiteboard Specification - Support for the development of REST-style microservices is provided through the integration of JAX-RS technology in the JAX-RS Whiteboard Specification. This defines a model to provide microservice endpoints using the OSGi services-based whiteboard model. See JAX-RS Whiteboard Specification.

Web Applications Specification - The Web Application specification provides support for web applications written to the Servlet 2.5 specification as well as the JSP 2.1 specification. This specification details how web applications packaged as a WAR or as bundles (WABs) can be installed into an OSGi framework, as well as how this application can use OSGi services. See Web Applications Specification.

Http Service Specification - Bundle developers typically need to develop communication and user interface solutions for standard technologies such as HTTP, HTML, XML, and servlets. The Http Service supports two standard techniques for this purpose: registering servlets and registering resources. See Http Service Specification.

Http Whiteboard Specification - The [1] Whiteboard Pattern pattern has shown to be a powerful and flexible mechanism for registering customized functionality with a container. The Http Whiteboard Specification allows the registration of Servlets, Servlet Filters, Resources and Servlet-related listeners via the Whiteboard pattern, providing a convenient approach to working with servlets to the Http Service Specification. See Http Whiteboard Specification.

Event Admin Service Specification - The Event Admin service provides an inter-bundle communication mechanism. It is based on a event publish and subscribe model, popular in many message based systems. See Event Admin Service Specification.

Asynchronous Service Specification - Asynchronous processing can be the key to scalability for large enterprise applications, especially under heavy load. OSGi Services have traditionally followed the Java interface-based design which by default provides synchronous semantics. The Asynchronous Services specification adds an asynchronous programming model to new and existing OSGi services. See Asynchronous Service Specification.

Promises Specification - Many JavaScript applications use Promises-based APIs to facilitate asynchronous processing of a workflow in which executions are time consuming or subject to waiting for I/O operations. The Promises specification defines a Promises API for use in OSGi applications. The Promises API is used by other specifications, such as the Asynchronous Services specification, but can also be used independently. See Promises Specification.

Push Stream Specification - This specification defines a library supporting the handling of push-based event streams. It focuses on reactive programming and builds on the Promises specification. As with Promises, the Push Streams can be used both inside an OSGi framework as well as outside. See Push Stream Specification.

Management Model Specification for JMX™ Technology - The Java Management Extensions (JMX) is the standard API specification for providing a management interface to Java SE and Java EE applications. This specification provides an MBean interface adaptation of the existing OSGi framework artifacts; these can then be used to expose an OSGi Framework manipulation API over JMX. See Management Model Specification for JMX™ Technology.

REST Management Service Specification - REST is a powerful paradigm for accessing resources over a network and is widely used in Enterprise and Cloud settings as a protocol of choice, especially since it generally avoids problems with internet firewalls, from which other protocols may suffer. The REST Management Service Specification provides an API to manage and control an OSGi framework using REST operations. See REST Management Service Specification.

User Admin Service Specification - The User Admin Service Specification provides authorization for OSGi framework actions based on authenticated users, instead of using the Java code-based permission model. See User Admin Service Specification.

Initial Provisioning Specification - This specification defines how the Management Agent can make its way into the OSGi framework, and gives a structured view of the problems and their corresponding resolution methods. The purpose of this specification is to enable the management of a OSGi framework by an operator, and (optionally) to hand over the management of the OSGi framework later to another operator. See Initial Provisioning Specification.

Configuration Admin Service Specification - The Configuration Admin service allows an operator to set the configuration information of bundles. See Configuration Admin Service Specification.

Metatype Service Specification - The Metatype specification defines interfaces that allow bundle developers to describe attribute types in a computer readable form using metadata. It is mostly used in conjunction with the Configuration Admin Service. See Metatype Service Specification.

Configurator Specification - The Configurator Specification defines a convenient way to provide Configuration Admin with configuration information based on JSON-based resources in bundles. It specifies the format of the JSON configuration resources, and defines how these are processed and submitted to the Configuration Admin service. See Configurator Specification.

JNDI Services Specification - The Java Naming and Directory Interface (JNDI) is a registry technology in Java applications, both in the Java SE and Java EE space. JNDI provides a vendor-neutral set of APIs that allow clients to interact with a naming service. See JNDI Services Specification.

Data Service Specification for JDBC™ Technology - provides an API for applications to interact with relational database systems from different vendors. See Data Service Specification for JDBC™ Technology.

JPA Service Specification - The Java Persistence API (JPA) is a specification that sets a standard for persistence in enterprise and non-enterprise JRE™-based environments. The JPA Service Specification defines how bundles may access and use JPA persistence units in applications, as well as how a JPA implementation can become available and be invoked within an OSGi framework. See JPA Service Specification.

JTA Transaction Services Specification - This specification provides the User Transaction, Transaction Manager, and Synchronization Registry services, which are based on their counterparts in the Java EE™ JTA Specifications. These services can be used to demarcate transaction boundaries, enlists durable and volatile resources, and provides transactional aware code to influence the outcome of a transaction and synchronize with the ending of a transaction. See JTA Transaction Services Specification.

Transaction Control Service Specification - This specification adds a concise and convenient programming model to work with ACID Transactions. Rather than taking a purely declarative approach as is done in some other Transaction solutions, the Transaction Control Service Specification defines a simple programming model to execute specific parts of code under transactional scope. It works very well with Java™ lambdas. See Transaction Control Service Specification.

Log Service Specification - Provides a general purpose message logger for the OSGi framework. See Log Service Specification.

XML Parser Service Specification - Addresses how the classes defined in JAXP can be used in an OSGi framework. See XML Parser Service Specification.

Service Loader Mediator Specification - Addresses common problems of bundles that rely on the JRE provided Service Loader API to load custom Service Provider Implementations. This specification describes how to use the service registry for lookup of Service Providers as well as a solution for existing code to continue functioning using Service Loader API in a OSGi environment. See Service Loader Mediator Specification.

Coordinator Service Specification - The Coordinator service provides a mechanism for multiple parties to collaborate on a common task without a priori knowledge of who will collaborate in that task. The service provides a rendezvous for an initiator to create a Coordination where collaborators can decide to participate. When the Coordination is ended, all participants are informed. See Coordinator Service Specification.

Converter Specification - The Converter Specification provides a uniform API to convert a given Java object into a myriad of other representations. Conversions include from untyped data, such as a configuration map, into a typed instance such as an annotation or interface. Or between various types of scalars, arrays or collections. The converter can also be customized to perform domain-specific conversions. See Converter Specification.