It isn't clear how page scoped resources are cleaned up. They appear to survive
multiple requests, however can be out of date and require a refresh() as indicated in the
issues example ProjectFinderBean class.
Is it possible to set a page scope timout so that resources can be cleaned up in addition
to providing a way to schedule data refreshes without user interaction?
The docs seem to imply that page scoped state is serialized back to the client, so maybe
no data is being stored on the server. This might aliviate memory related issues, but
having a declarative way to time out this "page cache" would seem beneficial.
Am I missing a configuration option?
An example use case might be a stock quote. A company may have an investors page that
uses a third-party web service to lookup the company's stock price every 5 minutes.
This request should only be made once every 5 minutes, users shouldn't be able to
refresh, and it should be easy to implement. Seam + page scope + @Factory seems ideal
here. If you can time out the data that is. After the time out, the factory method would
be called again, and round you go.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3970848#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...