You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Configuration Properties

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

Common properties

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

The Intent Map

remote-services.xml files

  • No labels