Hi Sebastian, I think that service layer have to be responsible only for CRUD operations, but L(list) operations should be built upon JPA-specific _READ-ONLY_ queries or some kind of DSL (for example, querydsl http://source.mysema.com/display/querydsl/Querydsl). The last one point allows to build quite complex queries w/o affecting service layer.
So we have: 1. fine-graned business logic separated by service interface 2. service interface implementation incapsulates CRUD-operation 3. data provider uses specific service interface (in case of simple objects list) or "query dsl" Hopes it helps a little :) -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/OT-Best-practices-regarding-service-layers-DAOs-tp2400408p2400436.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
