The first, most direct connection to OSGi is the bean that’s created on your behalf when you export a service. This bean, an instance of:-

By default, beans created in a Spring application context are global to the entire OSGi runtime.

To create services and have those automatically installed in the registry.

Element to export the bean as an OSGi service, classified by the interface we specify.

These beans are proxies, some may load asynchronously or take a longer time to register. <osgi:service interface="com.apress.springrecipes. osgi.helloworld.service.GreeterService"> <bean class="com.apress.springrecipes.osgi.helloworld. service.GreeterServiceImpl"/> </osgi:service>

An anonymous bean specified inside of the osgi:service element allows you to avoid cluttering the namespace.

Sometimes, you may want to limit the visibility of a service so that multiple clients each get their own instance of the bean.

Spring Dynamic Modules also supports injection and manipulation of bundles themselves. An injected bundle is of type:-

Once acquired, the Bundle can be interrogated to introspect information about the bundle itself, including any entries, its current state.

OSGi will let you maintain multiple versions of a service in your registry at the same time.

Multiple services of the same interface may be registered inside of an OSGi environment, which necessitates a conflict-resolution process.

When specified on a service element, allows the ascription of a rank relative to other beans with the same interface.

A more robust solution to service discrimination is service attributes.

There are frequently situations where OSGi will return more than one instance of a service that satisfies the interface.

Attribute, which, is the symbolic name of another bundle.