Editing OSGi (section)

===Standard services===
The OSGi Alliance has specified many services. Services are specified by a [[Java interface]]. Bundles can implement this interface and register the service with the Service Registry. Clients of the service can find it in the registry, or react to it when it appears or disappears.

The table below shows a description of OSGi System Services:<ref>{{Cite journal |last1=Diaz Redondo |first1=R. P. |last2=Vilas |first2=A. F. |last3=Cabrer |first3=M. R. |last4=Pazos Arias |first4=J. J. |last5=Lopez |first5=Marta Rey |date=2007-02-01 |title=Enhancing Residential Gateways: OSGi Service Composition |journal= IEEE Transactions on Consumer Electronics|volume=53 |issue=1 |pages=87–95 |doi=10.1109/TCE.2007.339507 }}</ref>
{| class="wikitable" width = "100%"
! System Services
! Description
|-dsafassafasfas
| '''Logging'''
| The [[Java logging framework|logging]] of information, warnings, debug information or errors is handled through the Log Service. It receives log entries and then dispatches these entries to other bundles that subscribed to this information.
|-
| '''Configuration Admin'''
| This service allows an operator to set and get the configuration information of deployed bundles.
|-
| '''Device Access'''
| Facilitates the coordination of automatic detection and attachment of existing devices. This is used for Plug and Play scenarios.
|-
| '''User Admin'''
| This service uses a database with user information (private and public) for authentication and authorization purposes.
|-
| '''IO Connector'''
| The IO Connector Service implements the [[Connected Device Configuration|CDC]]/[[CLDC]] <code>[http://java.sun.com/javame/reference/apis/jsr118/javax/microedition/io/package-summary.html javax.microedition.io]</code> package as a service. This service allows bundles to provide new and alternative protocol schemes.
|-
| '''Preferences'''
| Offers an alternative, more OSGi-friendly mechanism to using Java's default {{Javadoc:SE|java/util|Properties}} for storing preferences.
|-
| '''Component Runtime'''
| The dynamic nature of services—they can come and go at any time—makes writing software harder. The Component Runtime specification can simplify handling these dynamic aspects by providing an XML based declaration of the dependencies.
|-
| '''Deployment Admin'''
| Standardizes access to some of the responsibilities of the management agent.
|-
| '''Event Admin'''
| Provides an inter-bundle communication mechanism based on a publish-and-subscribe model.
|-
| '''Application Admin'''
| Simplifies the management of an environment with many different types of applications that are simultaneously available.
|}
The table below shows a description of OSGi Protocol Services:
{| class="wikitable" width = "100%"
! Protocol Services
! Description
|-
| '''HTTP Service'''
| Allows information to be sent and received from OSGi using [[HTTP]].
|-
| '''UPnP Device Service'''
| Specifies how OSGi bundles can be developed to interoperate with [[Universal Plug and Play]] (UPnP) devices.
|-
| '''DMT Admin'''
| Defines an API for managing a device using concepts from the [[Open Mobile Alliance]] (OMA) device management specifications.
|}
The table below shows a description of OSGi Miscellaneous Services:
{| class="wikitable" width = "100%"
! Miscellaneous Services
! Description
|-
| '''Wire Admin'''
| Allows the connection between a Producer service and a Consumer service.
|-
| '''XML Parser'''
| The XML Parser service allows a bundle to locate a parser with desired properties and compatibility with [[JAXP]].
|-
| '''Measurement and State'''
| The Measurement and State service allows and simplifies the correct handling of measurements in an OSGi service platform.
|}