Hi, You are completely right Peter. We still need this functionality. My opinion is that there should be a "factory" config, that never changes, one current config and after an update of config, a latest config, to make it easy to revert to latest working.
/Jan ----- Original Message ----- From: "Peter Neubauer" <[EMAIL PROTECTED]> To: "General OPS4J" <[email protected]> Sent: Friday, February 23, 2007 9:03 AM Subject: Re: Adding optional properties to pax-ConfigAdmin > Hi Dave, > we have some similar requirement for our platform at my old employer. > There should be a default config that can be reverted to, and then the > current state of the config should be saved across different > invocations of the framework instance, and different states should be > able to be saved as config snapshots. Not sure how that is solved now, > I think Edward was involved in that? > > /peter > > On 2/23/07, David Leangen <[EMAIL PROTECTED]> wrote: >> >> I was having a discussion with Boon Ping recently regarding optional >> properties. >> >> The problem is this: >> >> I want to have default properties for a bundle sitting in a >> properties file that is committed to the svn repository (as is done >> presently). >> >> In addition, I want each user/developer to have the possibility of >> using an optional properties file if they want to change any of the >> default values. Such optional properties file would only be saved >> locally on that developer's machine so it would not "interfere" with >> anybody else. >> >> Upon startup, pax-ConfigAdmin would first check for the existence of >> such optional file. If it exists, these would override the props of >> the default file. Otherwise, it would use the props in the default >> file (if any). >> >> >> I think this is a reasonable use case, but Boon Ping does not. >> >> >> wdyat... could something like this be a candidate for pax-ConfigAdmin? >> >> If so, can we go ahead and make this change? >> >> >> Cheers, >> Dave >> >> >> >> _______________________________________________ >> general mailing list >> [email protected] >> http://lists.ops4j.org/mailman/listinfo/general >> >> > > _______________________________________________ > general mailing list > [email protected] > http://lists.ops4j.org/mailman/listinfo/general _______________________________________________ general mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/general
