Once OSGi integration is completed, maybe this would work well with ConfigAdmin???
> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Niclas Hedhman > Sent: 4 September 2008 18:38 > To: [email protected] > Subject: Re: [qi4j-dev] Service configuration properties files > > > On Thu, Sep 4, 2008 at 6:29 AM, Rickard Öberg > <[EMAIL PROTECTED]> wrote: > > > I'm ok with this. Niclas, can I move the mentioned file? > > There are a few things to consider; > > 1. Changing the properties files in a runtime setup requires the > Configuration store to be MemoryEntityStore, otherwise it will pick > things from the persisted data store anyway. > > 2. We need a reasonable default "built-in" so that everything works > "out of the box" without any configuration. > > 3. Such reasonable default can probably be used for testcases, > otherwise we need to handle that from both within the IDE and Maven > build. > > 4. I think the proper solution to this perhaps the long-planned > PropertiesFileEntityStore, in which case configuration becomes Editor > changeable more naturally. > > > Otherwise, no direct objections. > > > Cheers > Niclas > > _______________________________________________ > qi4j-dev mailing list > [email protected] > http://lists.ops4j.org/mailman/listinfo/qi4j-dev > _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
