> > We need to get the libraries and extensions touched up as well, which mostly > means QRM. Niclas has some ideas on how to do that in a minimalistic > fashion, but if anyone has experience with OR mapping and wants to work on > it, it's an open field (Niclas, right?). If we can't get them updated fairly > shortly we will release Qi4j 1.0 Core separately from everything else, just > to get it out.
QRM is one piece of work. The easiest thing to do at the moment is to serialize entities as JSON and store serialized text in some table - reusing org.qi4j.entitystore.map.MapEntityStore. That of course looses all the wanted benefits of some folks (which is understandable) ... me included. Solution that was there before sort of smells as user has to go and do mapping on his own a task that should not be necessary as model information is available, so user should provide only what's missing or default is not what he wants. Solution that would be an ultimate solution (the OR mapping way) is a lot of work. What is your time-line there? Alex. _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
