Page Scope LifeCycle and Garbage Collection

dro_k Sep 20, 2008 9:20 PM

When does Seam/JSF remove the Components that have a PAGE scope when
1) Normal workflow of clicking/posting away from a page.
2) User abandons a page by closing the browser?

This also brings up another question. What's the difference between PAGE scope and a short running Conversation? Just surviving the redirects? And if all your actions are done on a single page (a single page form) does it ever make sense to use Conversations?

Thanks

1. Re: Page Scope LifeCycle and Garbage Collection

michaelcourcy Sep 20, 2008 9:35 PM (in response to dro_k)

Hi Drew,

As I understand Page scope means that the page context is serialized on the client side and unserialized to be restored when the form is posted.

http://docs.jboss.com/seam/2.1.0.A1/reference/en/html/concepts.html#d0e2595

Thus the page context is kind of longer than the Event context for instance as it last the rendering of the page plus the next request (as long as this request is posted).
Actions
2. Re: Page Scope LifeCycle and Garbage Collection

dro_k Sep 21, 2008 3:32 AM (in response to dro_k)

Michael,

Thanks for the reply.

It's completely optional to save the PAGE Scope state on the client (setting javax.faces.STATESAVINGMETHOD to client) but by default, the View Root is saved on the server side.

My question is when do these saved states expire when they are saved on the server? Are they saved in the Session? and how all these relate to Seam's PAGE scope.

cheers,
Drew
Actions

Go to original post