On May 24, 2012, at 16:16 PM, Bram de Kruijff wrote: > On Thu, May 24, 2012 at 3:50 PM, Marcel Offermans > <[email protected]> wrote: >> On May 24, 2012, at 15:01 PM, Bram de Kruijff wrote: >>> On Thu, May 24, 2012 at 2:24 PM, Marcel Offermans >>> <[email protected]> wrote: >>>> I would not say that is a workaround, but the way to do it. >>> >>> Agreed, it seems the way to do it. You just can't trust the metatype >>> service to be there. Not just because it may not be part of the >>> deployment, but also because if it is it's bundle may not be active >>> because the DeploymentAdmin stopped it. The "optional" dependency of >>> the AutoconfProcessor on Metatype is void. >> >> I agree. >> >> I'm not quite sure what you mean with the last sentence? The spec and our >> implementation both have MetaType as an optional dependency. > > I just meant that this spec defined situation means that as the one > writing configuration files, I can never assume that MetaType service > will be around. Thus, I must always define local OCDs (as we agree) > upon below. Given this situation, the fact that the spec says it may > optionally be there does not provide me with anything, so it just as > well could have been left out. At least taht is how I understand it > now :S
Indeed! The only thing that could happen is that you provide a configuration without OCDs, hope that MetaType is there, and accept that (probably) your whole configuration will be ignored, or that this causes a rollback of the complete install. Not something we would recommend though. ;) Greetings, Marcel _______________________________________________ Amdatu-developers mailing list [email protected] http://lists.amdatu.org/mailman/listinfo/amdatu-developers
