Installable Runtimes

org.eclipse.wst.server.core.installableRuntimes

This extension point is part of an interim API that is still under development and expected to change significantly before reaching stability. It is being made available at this early stage to solicit feedback from pioneering adopters on the understanding that any code that uses this API will almost certainly be broken (repeatedly) as the API evolves.

This extension point is used to install new runtimes from remote update manager sites.

<!ELEMENT extension (installableRuntime*)>

<!ATTLIST extension

point CDATA #REQUIRED

id    CDATA #IMPLIED

name  CDATA #IMPLIED>


<!ELEMENT installableRuntime (installableRuntime)>

<!ATTLIST installableRuntime

id             CDATA #REQUIRED

featureId      CDATA #REQUIRED

featureVersion CDATA #REQUIRED

featureSite    CDATA #REQUIRED

bundleId       CDATA #IMPLIED

bundleVersion  CDATA #IMPLIED

path           CDATA #REQUIRED>


The following is an example of an installable runtime extension point:
   

<extension point=

"org.eclipse.wst.server.core.installableRuntimes"

>

<installableRuntime id=

"com.myruntime.id"

featureVersion=

"1.0.0"

featureId=

"com.myfeature"

featureSite=

"xyz"

bundleId=

"com.ibm.mybundle"

path=

"/zips/myRuntime.zip"

/>

</extension>

The following is an example of using the installable runtime extension point but having the runtime archive as a data archive in the feature.
   

<extension point=

"org.eclipse.wst.server.core.installableRuntimes"

>

<installableRuntime id=

"com.myruntime.id"

featureVersion=

"1.0.0"

featureId=

"com.myfeature"

featureSite=

"xyz"

path=

"myRuntime-1.0.zip"

/>

</extension>

In the feature manifest and data entry should be entered for the runtime archive as well as an installhandler. The default install handler can be used which will install the data archive inside the feature. If the runtime archive is not packaged within the feature, then you need to map the archive path to a relative or absolute url to the site.xml