The logic of the boot process can be customized by defining a boot extension - such an extension can perform its own installation process instead of the default one. A boot extension can also be used to preserve the default boot logic implying the use of a startup bundles list file, but to load the startup bundles list file from a remote URL since the framework initially locates the startup bundles list file as a resource in the local file system.

A boot extension should implement the com.prosyst.mbs.framework.boot.Boot interface. A boot extension can:

• Introduce installation logic different from the one integrated in the framework, i.e. from getting the initial bundles from a startup bundles list file. Implement the needed operations in the performInstall method by using the BundleContext of the System Bundle, passed as method's argument.
• Provide access to a startup bundles list file available at a remote URL. Implement the getBootINI method returning an input stream to the remote startup bundles list file.

Next, to make the framework use your boot extension prior to starting the framework add the extension class to the JVM classpath and set the mbs.boot.extension system property to the name of the boot extension implementation class.