A subsystem archive is not a artifact understood by an OSGi framework. That is, you can't install it directly with BundleContext.installBundle; it must be installed via the SubSystem service. So I don't see it fitting into the Initial Provisioning spec directly.
But one could use IP to provision the subsystems implementation and then provision a "special" bundle that would be understood by the subsystems implementation as direction to install a subsystem archive. This would require the subsystem implementation to support such a mechanism. -- BJ Hargrave Senior Technical Staff Member, IBM OSGi Fellow and CTO of the OSGi Alliance [email protected] office: +1 386 848 1781 mobile: +1 386 848 3788 From: Cristiano Gavião <[email protected]> To: OSGi Developer Mail List <[email protected]> Date: 2013/08/23 13:44 Subject: [osgi-dev] Would subsystem (.esa) be elegible to be added in Initial Provisioning spec? Sent by: [email protected] hi, while investigating about initial provisioning for Subsystem I found the Initial Provisioning spec and org.eclipse.equinox.ip. The spec says that I can use a VM argument that points to a url that must return a ZIP file. and that it may contain only four types of dictionary entries: text, binary, bundle, or bundle-url. Would be the Initial Provisioning spec the right place to support the Subsystems initialization needs? thanks, Cristiano_______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
