If you do want to stick with this approach, persist the results in session, do search when form is submitted.
now, to clear results you can do it in two ways: if you do not link to that page from many sides, add an activation parameter on each external link that parameter can be anytthing so you know user just came from another page. or reverse situation, add a parameter to all your local links and reset results when it is missing. this is a general explanation, .. no time to paste some specific code .... Davor Hrg On Mon, May 19, 2008 at 11:53 PM, Todd Orr <[EMAIL PROTECTED]> wrote: > I have a Form and a Grid on my search page. The Form's success handler > populates a List results variable using an expensive query that I'd > like to not run on every Grid page navigation. To prevent unnecessary > query hits I use the @Persist annotation on the results var. The > getResults method is used as the source for the grid. This works well. > However, I'd like to not have the user's previous results (from > session) populate the grid when the page is hit later on in a user's > session after an initial search has been made. So, I change the > persist to use the flash strategy. However now the paging on the Grid > fails. > > I'd like to have the Grid be empty the first time the search page is > hit. I'd like the results to be saved so that the search query doesn't > need to be run unless the form is submitted. I'd like to be able to > page through the results in the Grid. > > What is the recommended approach to solving this case? > > Thanks, > T > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
