Hi Scott,
What Sven mentioned could help.
If it is a Page variable you need to persist, you could also put it in the
HttpSession:
getContext().setSessionAttribute("variable", 123);
regards
Bob
On Tue, Nov 19, 2013 at 11:14 PM, Scott Gurney <[email protected]> wrote:
> Thanks, Gilberto. I should have been clearer and maybe in my ignorance I
> am missing something quite simple. You see, I am having issue with the
> state of the page. Not the state of the table. The request parameter is
> bound to a page public variable. If I save the state of the table it does
> not save the request parameter. Does that make sense?
>
> Scott
> [email protected]
>
> On Nov 19, 2013, at 3:31 PM, Gilberto <[email protected]> wrote:
>
> In the Advanced Table example[1] you will find sample code to preserve
> state[2] between requests.
>
> Regards,
>
> Gilberto
>
> [1]
> http://click.apache.org/docs/user-guide/htmlsingle/click-book.html#advanced-table
> [2]
> http://click.apache.org/docs/click-api/org/apache/click/control/Table.html#saveState(org.apache.click.Context)
>
>
>
> 2013/11/19 Scott Gurney <[email protected]>
>
>> I'm looking for some guidance from any Click users who have used Click
>> Tables in their work. In particular, I'd like to know any "rules of thumb"
>> for designing pages (or sequences of pages in a workflow) so that table
>> pagination works consistently.
>>
>>
>>
>> You see, I have a first version of a relatively simple application built
>> using Click. In one sequence of pages in a workflow, I'm using a request
>> parameter from the query string to dynamically choose the data to display
>> in a table of results. The obvious problem with this approach is table
>> pagination doesn't function properly because the original query string is
>> not maintained between requests. So page 1 of the table works but none of
>> the other pages in the table do.
>>
>>
>>
>> Anyone else run into this, choose to continue using request parameters,
>> and find an elegant way of saving state? I'm second-guessing altogether my
>> approach of using a request parameter for this purpose.
>>
>>
>>
>> Any thoughts are appreciated.
>>
>>
>>
>> Scott
>>
>> [email protected]
>>
>>
>>
>
>
