Update to my problem: Adding action="pageControllerBean.action" fixed the pagination problem. This is strange, maybe a bug? The initial result set that I was trying to paginate was being managed by a stateful session bean that encapsulated an EntityQuery object. I had some logging code in the search() method of my bean to display the query parameters, and everything looked as I suspected -- however I could not get my page to sort or paginate correctly until I added the attribute action to the link. So my source went from: <s:link view="/DeliverableSearch.xhtml" | rendered="#{deliverableSearch.previousExists}" | value="#{messages.left}#{messages.left} First Page" | id="firstPage"> | <f:param name="firstResult" value="0"/> | </s:link> To: | <s:link view="/DeliverableSearch.xhtml" action="#{deliverableSearch.search}" | rendered="#{deliverableSearch.previousExists}" | value="#{messages.left}#{messages.left} First Page" | id="firstPage"> | <f:param name="firstResult" value="0"/> | </s:link> I added the same action attribute to the link that sorted the data as well. This fixed both the pagination and sorting issue. The question is, why was the page not performing as expected before, when clearly I know the search method on the bean was being called because I could see the output in the log file... Best Regards, MG View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4099478#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...