Marty - thanks for the help.
Actually even with client state saving, the Trinidad framework save state
on the server (and actually, I have the State saving method set to client)
and just a token on the client. I'm not sure of all the things going on
here, I'm just reporting what I am seeing.
Scott - thanks for the pointer.
I actually ended up doing something very similar by using a feature of Seam
that in essence let's me do this without any extra coding on my part.
There is a feature called "Page Actions" that let's me associate parameters
(and a whole bunch of other stuff) with
Hey Chris, it's kind of hokey, but if your url contains all the data
you need you might be able to create a bunch of managed properties on a
managed bean and bind them to the request parameter mappings. You could
then use that managed bean to populate the values in your components. :)
Scott
That's what I was afraid the answer was going to be. I was hoping since
all of the data parameters were passed back in on the browser refresh that
there might be something I could do.
I've thought about the increasing the timeout (which is 30 minutes right
now), however to make sure the user
I have a generic search screen (standard input form) that displays the
results on the "next" page using a .
If the user hits the refresh button any time prior to the HTTPSession
timeout, then the form is resubmitted and the search generated again (could
display different results if the underly
5 matches
Mail list logo
