On Fri, Feb 4, 2011 at 4:32 PM, Paul Merlin <[email protected]> wrote: > Quoting Niclas Hedhman <[email protected]>: >> Are you arguing that we should possibly have a simple Indexing/Query >> implementation, mostly suitable for samples and tests? > > Exactly. > > >> And if so, we could stick that into qi4j-testsupport to indicate that >> it is not meant for production systems? > > That could be a solution, but on the other hand is using a "not meant for > production" implementation in unit tests a must ?
No, but just to indicate that "if you need indexing/query in your tests, you can use this one", and by that avoid the cross library<->extension dependency problem. It is only an issue for things in qi4j-libraries, AFAICT. >> Other solutions of cross libraries and extension dependencies is 'out >> of bounds' for discussion. >> >> If so, I suggest that you create a Jira ticket, and perhaps even start >> looking at an implementation ;-) > > Fair enough, I'll create the Jira ticket and will probably take a look at an > implementation when I have time. > > Is someone interested and could give a hand or throw some ideas ? I intend to implement a Hazelcast backed indexing/query system in the 'near future', so I will need to dig into what this entails to quite some depth and perhaps an "MemoryIndexer" is a good starting point. Cheers -- 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/24svnvk I relax here; http://tinyurl.com/2cgsug _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
