Le lundi 30 novembre 2009 16:58:35, Niclas Hedhman a écrit : > Hi, > > Can you give an honest opinion of the "quality" involved here, in terms of > code, docs, tests and longer term maintenance? > > If these are "on top" then *I* am Ok to keep it in qi4j-extensions... If > you feel something isn't right enough, then I suggest that the commit is > removed (you can it yourself I think). > > WDYT?
Given the fact that I mapped a MapEntityStore to a Hazelcast DistributedMap there's not so much code so I can argue that quality is good without much risk :) I used the Qi4j built-in facilities to unit test the code, copy/pasted/adapted what I found in entitystore-jdbm. There's no documentation at all but I sure can improve it. Now, about the longer term maintenance... I played a lot with Qi4j and I'm convinved to use Qi4j in my personnal projects. Given the code size I'm confident I'll be able to keep it up to date with both Qi4j and Hazelcast. Maybe the better is that you give the code a little read (it's really short). Paul _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
