I have committed my work to support paging. It is based on your suggestions with PagingParameter/PagedResult. It should work with any access objects. findAll, findByQuery, findByCriteria and custom access objects.
Paging is defined in the model by adding a PagingParameter as parameter to a repository operation. findAll; // without paging findAll(PagingParameter pagingParameter); // with paging For findAll it is possible to use a config property in sculptor-generator.properties to say that paging should always be used, i.e. not necessary to add the PagingParameter. findAll.paging=true For findByQuery it uses a "replace" naming convention for the counting (to calculate maxPages). findByQuery on named query "Person.findByCountry" will try to use "Person.countByCountry". For findByCriteria and custom access objects the developer must define the count operation or named query to use. That is done with a hint countOperation or countQuery. myPagedFindOperation(PagingParameter) hint="countOperation=myPagedCountOperation" delegates to AccessObject; Those hints are available for findAll and findByQuery also. See also PersonRepositoryTest junit test in library sample. I will describe this in wiki later. Ok? /Patrik -- View this message in context: http://www.nabble.com/-sculptor--pagination-tp20636538s17564p25949938.html Sent from the Fornax-Platform mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Fornax-developer mailing list Fornax-developer@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fornax-developer
