On Sun, May 16, 2010 at 4:39 AM, Anton Podviaznikov <[email protected]> wrote:
> I'm stack with Neo4j support now. I know that there is extension (I guess > this http://dscm.ops4j.org/git/gitweb.cgi?p=qi4j-extensions.git;a=tree;f=entitystore-neo4j;hb=396075ff031b263fa81d7fb870919a21d741c4be?) > but it uses outdated version of Neo4j. I will leave the Neo4j specific questions to someone from Neo Technology who would know more about it. > Does somebody has few more samples of using this db? In principle, once the assembly is done, there is no 'leakage' of Neo into the Qi4j world and there are no "Neo4j specific" samples to make. > I just need to specify needed implementation in the stage of the assembling? > What EntityStoreService will be used if I add MemoryEntityStoreService > and NeoEntityStoreService? It is all about "Visibility". A unit of work will use the EntityStore that it can see (at least for now) and you do that by modularizing your application appropriately. For instance, perhaps you want all the configuration in a separate store (like Preferences one), so you could create a module (or layer), where the Configuration entities are Visibility.application and a Preferences EntityStore with Visibility.module. That way, even if there is a EntityStore with Visibility.layer it won't be used for the Configuration entities. If there are more than one ES service of the same visibility, an ambiguity exception will be thrown (can't recall exact name). 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
