Hi List, The Auto Configuration Specification (compendium, section 115) shows a resource processor for use in Deployment Admin, which allows deploying configurations into Configuration Admin. The basic workflow of Deployment Admin is roughly like this, - install all bundles, but don't start them, - start all resource processors (marked with 'DeploymentPackage-Customizer' in their manifest), - feed all resources to the resource processors, - start the rest of the bundles.
If I now have both a Config Admin, an AutoConf processor, and some configurations in my deployment package, the Config Admin would only be started once all resources have been processed, but this would mean the AutoConf processor cannot find the Config Admin to put the configurations on. So, this cannot work. Is this an oversight in the spec, or is there a technical reason to disallow this? In a more general sense, I can see other situations in which I would have resources, their related processor, and the 'receiving bundle' for the resources in a single deployment package. Is this something we want to support, or should the receiving bundle just also pack the resource processor? Thanks, Angelo _______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
