Michael Hunger wrote: > I looked at the Sparql-Implementation. This is essentially an expression tree > formatter which could be done via a > visitor for any qi4j queries that is then implemented by the different > formatters (I did this with jequel - adding > double dispatch to the expressions was no problem at all, one could also have > a expression tree iterator which calls > callback hooks on the formatter). > > I also looked at the RdfEntityFinder. As the three methods are almost the > same, I'd suggest an approach that uses an IoC > callback (like in springs jdbctemplate) where only the dynamic part of the > result parsing is handled by the callback > and all the query creation/preparation/resource handling by one single method > accepting the callback. > > I'd offer to to this if you're interested.
Excellent! Alin started it, and I have done some minor refactorings, but none of us are actively working on it, so feel free to "take the lead" on this one. While you're at it, I think Edward is exploring how to do collections properly in the index/query, so you may want to sync with him on that. Edward, status? thanks, Rickard _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
