Hi, > Sure, that's what the platform does ... unfortunately, it's not quite > trivial. For full generality it would be necessary to take into account > what's available in the target platform -- you could start by > transporting your mobile bundle to the other side and then use the > framework to find out what's still missing. The package admin service > should be useful for that purpose. That way you could avoid > re-implementing the part of the framework that identifies which bundles > can provide which dependencies (there are at least two ways for a bundle > to declare those dependencies: the Require-Bundle:-header and the > Import-Package:-header, additional dependencies may be undeclared if > Dynamic-Import-Package is used). Another aspect of the problem relates > to your other question: which dependencies *can* be transported and > which must to be proxied? > > Harald For the sake of simplicity, we assume that bundle imports other dependent packages statically by declaring via statement import-package in its manfifest file and let avoid dynamic-import package. I took a quick a glance at Package Admin Service as you suggested but as far as I know, we can only extract information about packages that the bundle export via function getExportedPackages(Bundle ...). There is also a funtion getRequiredPackages() but the function returns what I do not expect to have but its return are all standard system packages that all bundles are required to import. Still my question is that I would like to acquire all bundles that contain all packages that the concerned bundle imports via the typical statement Import-Package in its manifest file. Anyone can help me or show me what I did misunderstand.
Regards, Conan. -- Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer _______________________________________________ OSGi Developer Mail List [email protected] http://www2.osgi.org/mailman/listinfo/osgi-dev
