I have fixed this in our oaw5_migration branch (version 1.8). http://fornax.itemis.de/jira/browse/CSC-464 CSC-464 .
It would be unwise to do this change in 1.7.0, so I wont. Another workaround is that you define your own type in sculptor-generator.properties: javaType.PagedResultPerson=org.fornax.cartridges.sculptor.framework.domain.PagedResult<org.fornax.cartridges.sculptor.examples.library.person.domain.Person> Then you can define the service operation like this: PagedResultPerson findByAgeAndStatus(Integer age, String status, PagingParameter pagingParameter); /Patrik Patrik Nordwall wrote: > > This looks like a missing feature in the DSL. I will take a look at it and > see what I can do. Maybe not possible to make it in 1.7.0 though. > > A workaround for you is that you move the entire method to the repository > and use delegation in service, i.e. > > Service PersonService { > findByAgeAndStatus => PersonRepository.findByAgeAndStatus; > } > > Repository PersonRepository { > PagedResult findByAgeAndStatus(Integer age, String status, > PagingParameter pagingParameter); > } > > Note that the return type is specified as PagedResult, but the generated > java type will be PagedResult<Person> > > /Patrik > -- View this message in context: http://old.nabble.com/-Sculptor--Specifying-PagedResult-for-a-service-operation--tp27057133s17564p27102677.html Sent from the Fornax-Platform mailing list archive at Nabble.com. ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Fornax-developer mailing list Fornax-developer@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fornax-developer