Dennis Byrne wrote:
with saveState, you can store whatever you can reach with a
value-binding - it is then serialized to the client side or
server
side session and reread/reloaded upon posting back the value
to the
server.
... but only , as Martin probably knows, if saveState is a
player in the next response.
Dennis Byrne
which means you trigger an ajax request, and lose your savestated bean ;-)
but besides that problem which I have not found a workaround yet, it is
nice to use... have been using it the last two days, it was a huge
timesaver.
