Bin Conan wrote: >> This leads me to believe that weak migration is quite feasible in >> an OSGi platform (just grab the bundle's bytes, e.g. using the >> Bundle-Location: header, and send them elsewhere) while strong >> migration is probably to hard to be useful. >> >> From the header of one bundle, can we determine that from which >> bundles the regarded bundle depends from? I only know that there >> is a statement Import-packages that declares which packages the >> bundle use. In other words, how can we define those imported >> packages belong exactly to some other specific bundles and it is >> possible to find those bundles?
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 _______________________________________________ OSGi Developer Mail List [email protected] http://www2.osgi.org/mailman/listinfo/osgi-dev
