Hi Neil,

Actually I want not to call update on Configuration object because in that
way the configuration will go to internal configuration store of
ConfigAdmin. I just want when getConfiguration is called and nothing is
found in internal configuration store of ConfigAdmin, to hook exactly there
another implementation which will go to an external storage and get what I
need. Is this achievable and how is the best way to do that in the Equinox
implementation?

Best regards,
   Philip Yankov

On Fri, May 13, 2011 at 3:29 PM, Neil Bartlett <[email protected]> wrote:

> Hi Philip,
>
> The normal way to hook config admin into an external data storage is
> to write a management agent that *calls* getConfiguration() and
> supplies the data via an update to the Configuration object. That way
> your agent can work with any config admin implementation.
>
> Typically config admin implementations use their own internal storage
> area for persistence. If you want to customise that internal storage
> then you may need to write your own implementation (though I think at
> least the Felix implementation has an extension mechanism so you don't
> have to write the whole thing).
>
> Regards,
> Neil
>
> On Fri, May 13, 2011 at 12:43 PM, Philip Yankov <[email protected]>
> wrote:
> > Hi,
> >
> > Is it possible to get a notification when
> > ConfigurationAdmin.getConfiguration( with any pid ) is called and return
> a
> > configuration from an external storage then? Are you aware of existing
> > mechanism to achieve this? Alternatively, we thought of pluging a hook
> > inside getConfiguration() method, or directly extending
> > ConfigurationAdminImpl and registering it instead of the current service
> > (ConfigurationAdminImpl should be made public though). How do you think,
> > what would be the preferred approach?
> >
> > Best regards,
> >   Philip Yankov
> > _______________________________________________
> > equinox-dev mailing list
> > [email protected]
> > https://dev.eclipse.org/mailman/listinfo/equinox-dev
> >
> >
> _______________________________________________
> equinox-dev mailing list
> [email protected]
> https://dev.eclipse.org/mailman/listinfo/equinox-dev
>
_______________________________________________
equinox-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/equinox-dev

Reply via email to