This sounds like a general problem, not specific to Neo4j, and perhaps introduced in 2.0...
I intend to revisit the entire Entity Store SPI in the next few weeks, since there are a bunch of ideas floating around that will affect it; * Timeserires & History support * Event Systems (read, store, forward) as part of UoW. * Multiple Entity Types per Entity * Possibly "ID + Values" storage pattern. But thanks for noticing it. Niclas On Thu, May 24, 2012 at 4:38 PM, Tibor Mlynarik <[email protected]> wrote: > Hi, > > I am trying to run dci-cargo sample against Neo4j entity store. > It fails whenever a query is executed as result is always empty. > > My findings so far are: > > Entity store has to have concern StateChangeNotificationConcern > applied, otherwise indexing service is not notified about entity > updates so queries doesn't work. > But adding this concern into Neo4j store was not enough to make it > work. Concern is applied to EntityStoreSPI.applyChanges, but runtime > calls EntityStoreUnitOfWork.applyChanges. So spi.applyChanges have to > be called from NeoEntityStoreUnitOfWork.applyChanges ( see > DefaultEntityStoreUnitOfWork ). > > Now indexing service works together with Neo4j store, but sample still > fails to run. > There are other issues I am investigating... > > cheers, > > - Tibor > > _______________________________________________ > qi4j-dev mailing list > [email protected] > http://lists.ops4j.org/mailman/listinfo/qi4j-dev -- Niclas Hedhman, Software Developer http://www.qi4j.org - New Energy for Java I live here; http://tinyurl.com/3xugrbk I work here; http://tinyurl.com/6a2pl4j I relax here; http://tinyurl.com/2cgsug _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
