Of the three lifecycle extension points, only the lifecycle.application
extension point is supported on devices. In order to utilize lifecycle.application
to start bundles, the developer must extend the extension point com.ibm.rcp.lifecycle.application.startBundles
and provide the application ID and bundle ID attributes.
The application ID specifies the application that is associated with this extension, while the bundle ID field specifies the bundle to start when the associated application is started.
Below is an example of the OrderEntry web application making use of lifecycle.application
<bundle id="com.ibm.rcp.samples.orderentry.service" />
The OrderEntry plug-in has it's plug-in name as com.ibm.rcp.samples.orderentry.webapp
and it's extension ID for the extension point com.ibm.eswe.workbench.WctWebApplication
. Together, they are used as the application ID for the lifecycle plug-in. The attribute bundle ID indicates a bundle that needs to be started for the OrderEntry web application to run correctly.
For an eRCP application, identified by an org.eclipse.ercp.eworkbench.applications
extension, an extension ID is not required. Therefore, the application attribute in this extension is used as the application ID for the lifecycle plug-in. Note that only the application ID is used. Do not place the plug-in name of the eRCP application in front of the application ID. For example, the following extension identifies a bundle as an eRCP workbench application:
<application id="MySample.application" name="My Sample">
<views normal="mysample.views.SampleView" />
should be used as the application ID for the lifecycle plug-in
Finally, if a developer wishes a bundle to be started when the workbench starts, the lifecycle.application
extension can associate to the workbench application ID, org.eclipse.ercp.eworkbench
Parent topic: Packaging applications for distribution