Distributed OSGi Reference has been edited by David Bosschaert (Apr 08, 2009).

(View changes)


Configuration Properties

These properties are set on the Service Registration in the OSGi Service Registry.

Service Provider properties

Property Name Data Type Example Description
osgi.remote.interfaces String org.example.BarService,org.example.FooService * Denotes the interfaces to be exposed remotely. This is a comma-separated list of fully qualified Java interfaces that should be made available remotely. A special value of * can be provided meaning that all of the interfaces passed to the BundleContext.registerService() call are suitable for remoting.
osgi.remote.configuration.type String pojo Specifies the mechanism for configuring the service exposure. Possible values:
  • pojo configuration is driven from POJOs (Plain Old Java Objects) registered as Services with the OSGi service registry.
  • wsdl configuration driven from WSDL

pojo configuration type

When the osgi.remote.configuration.type=pojo property is specified, the following properties may also be specified.

Property Name Data Type Example Description
osgi.remote.configuration.pojo.address String http://localhost:9090/greeter The address at which the service with be made available remotely. If this property is not specified, this defaults to http://localhost:9000/fully/qualified/ClassName.
osgi.remote.configuration.pojo.httpservice.context String /auction If this property is specified, the OSGi HTTP Service is used to expose the service, rather than a dedicated Jetty HTTP Server. This property doesn't allow the specification of a port number, as this is provided by the HTTP Service. Depending on the OSGi HTTP Service used, this is configured in its own way. The Distributed OSGi distributions come with Pax-Web, for which configuration information can be found here: http://wiki.ops4j.org/display/ops4j/Pax+Web+-+Configuration, however other OSGi HTTP Service implementations are potentially configured differently.

Service Consumer properties

On the client side proxy, typically the same properties are set as on set service provider side. There are some additional properties too. Since the client-side proxy is registered by the DOSGi implementation, all these properties are read-only.

Property Name Data Type Example Description
osgi.remote boolean true This property is always set on a service proxy, indicating that the real service is remote.
org.apache.cxf.remote.dsw.client String   This property is set to the bundle name of the CXF-DOSGi implementation and can be used to find client side proxies created by the CXF DOSGi implementation.

The Intent Map

remote-services.xml files

Powered by Atlassian Confluence (Version: 2.2.9 Build:#527 Sep 07, 2006) - Bug/feature request

Unsubscribe or edit your notifications preferences