On Tue, Nov 10, 2009 at 10:32 PM, Jacek Sokulski <[email protected]> wrote:
> tried to fix entitystore-preferences to pass the tests and it seems that > there is a problem with either AbstractValueType hierarchy: > org.qi4j.runtime.types.DateType extends AbstractStringType and does not > override isString method() so isString return true; Both I and Rickard has independently come across this in the last few days. Rickard now claims that the fix is committed to source repository. > BTW. > I do not understand why *configuration* persistence is required for Jdbm > persistence to work. :-) Well, perhaps the number of configuration parameters for Jdbm are a bit too few to warrant using the Configuration mechanism. OTOH, I think it is good practice as it will give you a greater insight in how things really work under the hood. Tip: Place a "Configuration Layer" under the "Infrastructure/Persistence Layer", and in that layer have for instance an PreferenceEntityStore to store the persistence configuration. So, the issue is really to make sure that PrefES can operate without Configuration ES, I think. 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
