Hi Angelo,
See my inline comments...
On 3.3.2011 г. 11:49 ч., Angelo van der Sijpt wrote:
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),
At this stage, Deployment Admin will start all customizer bundles.
- 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.
If AutoConfig resource processor cannot work without Config Admin
service then just mark your Config Admin bundle as a customizer bundle
in the deployment package manifest.
ATB, Evgeni
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
--
-----------------------------------------------------------------------------------
Evgeni Grigorov . Senior Software Engineer/Development Tools
ProSyst Software GmbH
Tel. +359 2 953 05 88 . Fax +359 2 953 26 17
Mobile +359 895 300 305
http://www.prosyst.com . [email protected]
-----------------------------------------------------------------------------------
stay in touch with your product.
-----------------------------------------------------------------------------------
_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev
