On Wed, Mar 4, 2009 at 2:32 PM, Alex Shneyderman <[email protected]> wrote:
> Sorry, I am totally confused. I am not sure if you are suggesting some way > to fix it or you are explaining the impossibility of it being fixed? :-) I was explaining how it works. > In general, is this a reasonable approach? If not what is? No it is not. I am baffled over your determination to seek a solution way beyond where we expect people to look. What do you need? IUIUC, you want a non-transient index, which is provided by the Native Sesame store at the moment. If that doesn't work "out-of-the-box" then it is a bug, which we need to fix. > What confuses the hell out of me is why I need the indexer in the first place; > I have the entity store, why on earth would I need the indexer? I mean if > query > by id it goes straigth to the entity store but if I do findAll it > needs RdfQueryService Ok, "findAll" is probably not a particularly useful generic case (maybe I am wrong), and when you need it, you can stick those entities into a ManyAssociation of a known reference if you don't want to go through the Query. Nevertheless, that shouldn't stop from a working indexing solution. I have just shot up Qi4j again (after working a lot on another project) and will attend this issue (whatever it may be). Perhaps contact me on "hedhman" @ Gtalk for quicker turn-around on this. Cheers Niclas -- http://www.qi4j.org - New Energy for Java _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
