Browse Prior Art Database

Method to self uninstall OSGi bundles

IP.com Disclosure Number: IPCOM000012048D
Original Publication Date: 2003-Apr-03
Included in the Prior Art Database: 2003-Apr-03
Document File: 2 page(s) / 40K

Publishing Venue

IBM

Abstract

Method for OSGi bundle to perform self uninstall.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 53% of the total text.

Page 1 of 2

Method to self uninstall OSGi bundles

For the purposes of this publication OSGi is Open Service Gateway initiative framework and specification which facilitates the installation and operation of multiple services on a single services gateway (set-top box, cable or DSL modem, PC, Web phone, automotive, multimedia gateway or dedicated residential gateway). The specifications delineate Application Programming Interface (API) standards for a gateway platform execution environment. Services gateways must support these APIs in order to conform to the OSGi specification. The APIs address service cradle-to-grave life cycle management, inter-service dependencies, data management, device management, client access, resource management and security. Using these APIs, end-users can load network-based services on demand from the service provider while the gateway manages the installation, versioning and configuration of these services.

OSGi specification does not provide a standard method for a bundle to uninstall itself. Two of the commonly used methods to uninstall a bundle are a) manually uninstall the bundle using OSGi console and b) have a separate OSGi bundle whose sole purpose is to uninstall the desired bundle using OSGi API. The first option requires human intervention which may not be feasible in many situations. The second option requires the presence of another bundle which may not be desirable in small foot print situations.

An alternative to these two options is to allow the bundle to uninstall itself after the bundle has completed processing. This publication describes one way of allowing a bundle to uninstall itself.

At any given time an OSGi bundle can be in any of the following six sequential states : Installed, Resolved, Starting, Active, Stopping and Uninstalled. OSGi bundles can only be...