I use t:saveState for everything.
However, you could also use t:dataTable preserveDataModel="true".
As for t:saveState, here is an example of correct usage:
<t:saveState id="searchPageSearchResultList"
value="#{searchPage.searchResultList}" />
You want to save the state of your t:dataTable's value binding
(probably a list).
In your example, it'd probably be:
<t:saveState id="YourIdHere"
value="#{tabnavigering.aktueltVarsel}" />
You can place the t:saveState tag anywhere on the page (it's evaluated
at save state and restore state phases, so order doesn't matter). It
doesn't have to be on the same line, but t:saveState does not take
children. All t:saveState does is encode the value of the bean you
point it at into the component tree, then decode it on the next
request and assign it back to the value of the bean you point it at.
On 4/16/07, Brummeline Braaten <[EMAIL PROTECTED]> wrote:
Adrian Mitev <adrian.mitev <at> googlemail.com> writes:
>
>
> Try with tomahawk t:saveState
>
I've tried that, but I can't get it to work as intended. Perhaps I save the
wrong state? I tried to save the whole bean, but then nothing worked. Is there
some sort of rule of where the place the savestate tag? And does it have to be
closed on the same line or can I use savestate over an entire form-tag?
