Hello, What we actually need is to be able to use a custom configuration storage along with the ConfigAdmin's internal storage, without moving configurations from the custom storage to the internal storage. The goal is to use the ConfigAdmin's internal storage for global configurations, while the custom storage for more component-specific configurations. Both have nothing in common and should not be mixed up. We want to use the Equinox implementation of ConfigAdmin, without forking the code or reimplementing it. Could you propose a way to achieve this?
Regards, Lazar -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Neil Bartlett Sent: Friday, May 13, 2011 3:29 PM To: Equinox development mailing list Subject: Re: [equinox-dev] ConfigAdmin getConfiguration from external storage 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
