When exactly are request-scoped beans evicted from memory?

Question

Hi,
I have a question about request-scoped JSF-managed beans and request-scoped HibernateFilter. It seems to me that request-scoped JSF beans actually outlive an HTTP request. Here's what I mean. Let's say I have a page backed by a request-scoped bean #{myBean} which displays a dataTable. a user can click on a row to perform some operation on row data.
I always thought the following to be true about lifecycle of JSF request-scoped bean:
1.User makes initial page request
-HTTP Request 1 (R1) comes in
     1. RestoreView encounters #{myBean} in page and constructs MyBean
     2. RenderResponse renders the page
-R1 is terminated, page is displayed, myBean is evicted from memory
2.User looks at the dataTable and clicks on a specific row (via commandLink). Now MyBean.action() is supposed to be
executed and perform some operation on row data:
-HTTP R2 comes in
     1.MyBean is constructed again (e.g. not using same instance as in R1). (THIS IS KEY!)
     2.myBean.action() is executed
-R2 is terminated, myBean is again evicted from memory
Is the above understanding correct?
Or does myBean instance (and its' properties) remain in appserver memory between R1 and R2 and R2 actually uses the
same instance of myBean?
If scenario above is correct, then I have a strange problem:
-when performing myBean.action() during R2 on rowData (which is instance of MyHibernateBean) I get a
HibernateException stating that bean isn't associated with a Hibernate Session. This can only happen if the lifecycle of the object and its' parent myBean exceeded that of R1. That is because I have a Hibernate Servlet
Filter that a) start a Hibernate Transaction on incoming request and b) commits it on the way out.
Here's pseudo-code for myBean:
public class MyBean {
    public static String HANDLE = "#{myBean}";
    //getters setters omitted
    //used as 'value' in dataTable
    private List<MyHibernateBean> dataBeans;
    //dataTable binding
    private UIData tableData;
    public MyBean() {
    public String action() {
        //read children & modify state of a hibernate bean
        MyHibernateBean dataBean = (MyHibernateBean) this.tableData.getRowData();
        HibernateUtil.getCurrentSession().refresh(dataBean); //seems necessary as dataBean instance deemed 'stale'
        dataBean.getChildCollection(); //will fail without line above
        return "toSomewhereElse";
}

Answer 1

By the way, I have an hypothesis why this does not work...
The datatable values MUST be specified using a value binding expression. When the restoreState method for the component is called, JSF attempts to use the VB expression to get the table values. When the managed bean is not found, it creates a new (empty) one and the world ends (actually it just returns back to the original page because it cannot figure out what to do)