5.4.1. Pax Runner - Platform - Extender

Modules

5.4.2. Pax Runner - Platform - Felix

Overview

The platform extender tracks registration of platform builders. Once such a platform builder gets registred will install a new platform service corresponding to the platform builder. If a platform builder is unregistered will unregister the corresponding platform.
Distinction between the platforms can be done by using a filter while resolving the platform, filter based on the following platform properties:

• provider: the platform provider; expect something as equinox, felix or knopflerfish
• version: the platform version; dependes on the platfoem provider version.
  Onec you have a platform you can start it up via the start method with your bundles, properties and specific configuration options. Look to Javadoc for details.

Examples

• Get any platform

  bundleContext.getServiceReference( Platform.class.getName() );
  

• Get a felix platform

  bundleContext.getServiceReference( Platform.class.getName(), "(provider=felix)" );
  

• Get a felix platform with a specific version

  bundleContext.getServiceReference( Platform.class.getName(), "&(provider=felix)(version=1.0.0)" );
  

Platform Definition file

The platform definition file is an xml file file that is used to define the parts that makes up the platform.
The file has the following syntax:

<platform>
  <name>system_package_name</name>
  <system>system_package_url<system>
  <packages>system_packages_list</packages>
  <profile name="profile_name" default="true/false" [extends="parent_profile_name"]>
    <bundle>
      <name>bundle_name</name>
      <url>bundle_url</url>
    </bundle>
    ...
  </profiles>
</platform>

where:

• system_package_name : a nice name for the system package; optional (if not set the url is used as name)
• system_package_url : the url of the system package
• system_packages_list : optional; a comma separated list of packages to be appended to system packages
• profile_name : name of the profile
• default : one of the profiles should be marked as default. This is the profile to be used if no other profile is specified.
• parent_profile_name : name of the profile that is extended by this profile. Is optional and facilitates reuse
• bundle_name : a nice name for the bundle; optional (if not set the url is used as name)
• bundle_url : url of the bundle that makes up the profile. There can be more bundles in a profile.

To validate a definition file you could use the following XSD: TODO

Profiles

Profiles are a set of predefined set of bundles for a particular common usage scope. Such profiles could be minimal (default profile), logging, configuration, web,...
Every platform supports it's own set of profiles in platform specific way = using as much as possible platform specific bundles to archieve the intent of profile.
Each platform supports a default profile, profile that will be used when no profile option is specified. Checkout the platforms for a list of supported profiles.
The list of profiles to use can be specified via a configuration option (see bellow).

Configuration

The service can be configured in three ways, each having precedence over th other in the order thay are enumerated: via properties used when starting up the platform, via configuration admin if available and via framework/system properties.

Execution Environments

Name	Description
NONE	No aditional packages. Only the boot delegation will be used in this case (java.*)
CDC-1.0/Foundation-1.0	Equal to J2ME Foundation Profile
OSGi/Minimum-1.1	OSGi EE that is a minimal set that allows the implementation of an OSGi Framework
JRE-1.1	Java 1.1.x
J2SE-1.2	Java 2 SE 1.2.x
J2SE-1.3	Java 2 SE 1.3.x
J2SE-1.4	Java 2 SE 1.4.x
J2SE-1.5	Java 2 SE 1.5.x
JavaSE-1.6	Java SE 1.6.x
PersonalJava-1.1	Personal Java 1.1
PersonalJava-1.2	Personal Java 1.2
CDC-1.0/PersonalBasis-1.0	J2ME Personal Basis Profile
CDC-1.0/PersonalJava-1.0	J2ME Personal Java Profile

Modules

5.4.2. Pax Runner - Platform - Felix