Hi, all! I was waiting for the 0.6 hoping this will be fixed but not much changed and there is still a bug in
org.qi4j.index.rdf.assembly.RdfNativeSesameStoreAssembler it needs EntityTypeSerializer in addition to EntityStateSerializer (at least in my case there were complaints by qi) The frustrating thing that even when I add that I still can not get it to run. The same long trail of exceptions. Should I just abandon my efforts of trying to make it work? How do you guys persist? There are no tests doing native configuration. The tests are only for in-memory configuration and they work if you run a test where db files are removed on each run, the DB is created (and I guess this is what updates the index) anew and querying within the same JVM process (that is what the tests in qi's source-base do) but that is not exactly how persistence should work IMHO. I should be able to bring down jvm start a new one and be able to find my old friends. WDYGT? Note, also that the above will work and the data is still there on the consequtive runs but I have to update at least one entity to recalculate in-memory index. So, maybe I can nudge the indexer to re-index somehow? Any code sample would be appreciated. If there is an alternative way to search for entities, I would be happy to hear about them. Alternatively maybe someone could take a look at what I got and see if there is something really obvious that's incorrect (I could zip my sample up and send it to anyone who might be interested). Sorry for this long mail and thank you very much for any help. Cheers, Alex. >> My guess is that the indexing files are corrupted somehow. Can you look >> in /rdf-stores/rdf-indexing and clear those files, and see if that helps? > > No, I removed rdf-stores directory and it did not help. Same long > exception trail. > > Is there a functioning test case I can look at? Maybe comparing what's > working with what I have will clue me in on the differences. > > Thanks, > Alex. > _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
