On Wed, Jun 24, 2009 at 10:54 PM, Mads Brøgger Enevoldsen<[email protected]> wrote: > Yes. We do have a > org.qi4j.entitystore.jdbm.JdbmEntityStoreService.properties file which sets > the file name of the persistance file. The only reason for this activation > code is to override the file location (because it changes depending on the > platform). This could probably be solved in another way.
Ok, that is a valid usecase. The "problem" is that the EntityStores are a little bit different than most Services. They can't store the configuration entities in their own store, so there is always a second, configuration free, entitystore used by the Configuration of EntityStores. Confused? Typically (default) is a MemoryEntityStore, which means that it picks the config from the properties file and sticks it into RAM, hence your "drop". You need to assemble the JdbmEntityStore to use another ES for its configuration. That was the purpose of for instance the PreferenceEntityStore, using the JDK Preferences mechanism. That store is probably not 'upgraded' to 0.8-SNAPSHOT level yet, and I think it might pay best off for your case to fix up that store. Cheers -- Niclas Hedhman, Software Developer http://www.qi4j.org - New Energy for Java I live here; http://tinyurl.com/2qq9er I work here; http://tinyurl.com/2ymelc I relax here; http://tinyurl.com/2cgsug _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
