Java EE (Java Enterprise Edition) General Discussion

I have a JSF portlet that returns a set of paginated search results, up to 500, and uses the jsptags.com pager tag library to paginate the returned search results by 10 results per page. However, if I click Next to go to page 2, 3, 4, etc. the page offset seems to get stored in the session somewhere and any subsequent searches start the navigation on whatever page number last viewed on the previous search (page 2, 3, 4, etc.).

Has anyone seen any issues with the page offset getting stuck in the session? I tried searching both the PortletRequest and PortletSession objects for the page offset value to see if I can track down where it's being stored/cached.

Also, I can completely leave the portlet, come back, and enter completely new search criteria and the page offset value is still picked up from somewhere and I land on page 2, 3, 4, etc. of the search results. I'm not all that familiar with the jsptags.com pager tag library, so I'm not exactly sure where to look next. Let me know if you have any thoughts on where this value might be getting stored/picked up. Thanks!

Ryan

Edited by: ryaneye on Feb 9, 2009 1:05 PM