Hi Antonio,
On 2/25/15, 12:36 PM, "Antonio Sanso" <[email protected]> wrote: >Usually the person that set’s the OSGi configuration (aka the >administrator) is different than the one that >codes a bundle (aka the administrator). This can also happen in two >distinct phases of the project. >I have the impression that this feature mixes the concerns… I think that is a perfect example why we should have such a dependency mechanism, as the the phases are executed by different personas. As a developer I would like to specify that my component should only be started when the administrator has configured a subServiceName and that is ready to be used. Using "the Sling initial content in the same bundle" as the component is not always possible, for example if the component is 3rd party bundle. Also I am not sure there is a guarantee to always work. Even more, the solution relies on the fact the service user is configured by the “developer” but as you said this can be configured by an “administrator". As a side note I think we should even allow a component to be able to restart when a mapping is changed as its security context is changed. Marius
