It basically involves splitting the behaviour into an action and a view state with a transition between them called 'paginate'
loadResults {
action {
def criteria = MyDomain.createCriteria(){
eq('someField','someval')
}
flow.myDomainResults = criteria.list([max: 9, offset: flow.myDomainOffset ?: 0])
flow.totalMyDomains = flow.myDomainResults.totalCount
return success()
}
on('success').to('browse')
on(Exception).to "handleError"
}
browse {
on('paginate') {
flow.myDomainOffset = params.offset
}.to('loadResults')
on('selectItem').to('someOtherState')
//...
}
One point to note is that I use a criteria in order to get the totalCount property populated for me automatically so that I don't have to run a separate query. Also, the above only works if your domain class is Serializable, in my real application this wasn't the case so I stored a list of maps containing the properties I wanted to display instead of the list of domain objects.Then in the view all we need to do is to pass the current page from the flow scope to the paginate tag. The paginate tag also contains an extra parameter in order to trigger the paginate event when the generated links are clicked.
<g:each in="${myDomainResults}" status="i" var="myDomain">
<g:form action="myFlow">
<input name="id" value="${myDomain.id}" type="hidden">
URL: ${myDomain.url}
<g:submitbutton name="selectItem" value="Select"/>
</g:form>
</g:each>
<div class="paginateButtons">
<g:paginate max="9" offset="${myDomainOffset}" total="${totalMyDomains}" params="${[_eventId_paginate:true]}" />
</div>
You can also see I render each item as a separate form with a hidden id field and a submit button to trigger the 'selectItem' event and move onto the next state.I haven't tried messing with all the options for g:paginate to make sure they still work so please let me know if you find any problems with the above code.
