Hi Andrei,

Am Sonntag, den 05.06.2011, 16:08 +0100 schrieb Andrei Pozolotin: 
> Felix:
> -------- Original Message  --------
> Subject: Re: ConfigurationAdmin & SCR component self-update
> From: Felix Meschberger <[email protected]>
> To: [email protected] <[email protected]>
> Date: Sun 05 Jun 2011 07:41:28 AM CDT
> > Hi,
> >
> > Am Sonntag, den 05.06.2011, 06:49 +0100 schrieb Andrei Pozolotin: 
> >   
> >>     what am I missing? :-)
> >>     
> >
> > It is under your own control to break the recursion: Your component will
> > only have to call Configuration Admin configuration if such
> > configuration is not provided through the activate or modify method,
> > i.e. only if such update is induced externally.
> >   
> yes, this is what I came up with. it just feels odd there is no way to do
> Configuration.update(...) which does persist only but does not propagate
> to SCR.

This is how the two service are specified:
Configuration.udate(Dictionary)  must persist, update
ManagedService[Factory] services and send events to listsners.

SCR must forward configuration to components (unless the component is
configurationPolicy=ignore).

In your example, though, SCR was not involved at all, since your
component implemented a ManagedService which is called by
ConfigurationAdmin after update().

Regards
Felix

> > BTW: for your sample use case of UI location you might want to look into
> > the OSGi Preferences Service specification which sounds more appropriate
> > for such configuration (which generally is different per user).
> >   
> great idea. looking into it now.
> > Regards
> > Felix
> >   
> thank you.
> 
> Andrei.
> > Regards
> > Felix
> >
> >   
> >>     Thank you,
> >>
> >>     Andrei.
> >>
> >>     
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [email protected]
> > For additional commands, e-mail: [email protected]
> >
> >
> >   
> 



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to