So, if you have already created an instance of employeeBackingBean (and
it is defined as having a session scope), it should be available for all
subsequent pages in the session.
Correct. But I wouldn't think I'd need to have to give my backing bean session scope in order to accomplish this. Using Struts as an example, if I'm in my Action responsible for "getting an Employee" from the backend and I then shove it request scope, the Employee is now available on the resulting page that I forward to. I'm still a bit stumped how this is accomplished with JSF without using Session scoped backing beans. To reiterate the flow ...
"employees.jsp" - user clicks on edit employee link (passing in employee id)
backing bean "getEmployeeAction" method called returning an employee object from backend. (For simplicity lets just assume Employee object is in this EmployeeBackingBean).
navigation rule has us now forward to the "employeeForm.jsp" which should be autopopulated with the Employee information we returned in our backing bean. Can all of this be done with Request scope? I would think it should since it's pretty basic CRUD UI flow in applications.
--
