Alin Dreghiciu wrote: > There is one detail that I do not like to much: To be able to create a > query you have to start from a QueryBuilderFactory and this factory > you can only get it from a UnitOfWork. This makes sense for a query on > entities but for a query on iterables the unit of work is useless. So, > even if you want to do a query on iterable of composites you still > have to have a valid assembled unit of work.
If the iterable contains Entities (e.g. a ManyAssociation), then the UnitOfWork is definitely required. > Maybe it should be possible to get a query builder factory from > Module. In this case the newQuery() can either throw an exception and > let user know that he has to get the factory from the module if he > wants to use this method or use the module to get the unit of work > (current or new one?). This would only make sense if you want to do queries on plain Composites (or TransientComposites or whatever we renamed them to in the future), but I can see very limited use of that, compared to doing Queries on Iterables of Entities. Any examples? /Rickard _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
