While writing the documentation for Query, I was thinking that there seems to be a very big flaw...
To do ordering on the Query, you need access to the mixin templates, otherwise one can't pass the property to the QueryExpressions.orderBy() method. And if we are saying that the query is built in the domain layer and handed to a UI layer to do sorting and pagination... well, it can't be done... So, if we add that the Query also has the method templateFor() to retrieve the template to do the OrderBy functionality, I think we are Ok. WDYT? Cheers -- Niclas Hedhman, Software Developer http://www.qi4j.org - New Energy for Java I live here; http://tinyurl.com/2qq9er I work here; http://tinyurl.com/2ymelc I relax here; http://tinyurl.com/2cgsug _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
