Originally posted by Tim Holloway:
I might be missing something here, because I'm not quite able to visualize the beans, their contexts and their relationships withot printing the question out and looking at the big picture. But being lazy, first I need to ask a stupid question: You're not mistaking the meaning of "request" scope are you? Request scope beans are destroyed and recreated for EVERY page load.
I have to ask, since a superficial reading of your question sounds like you're expecting the first page load to construct data that will be visible on subsequent page loads, and for that you'd need session scope.
Maybe I should start with a different series of questions. What makes session scope beans more attractive than request scope beans? Because I am trying to avoid using session scope due to their extended stay in memory. What if I have a site where I am expecting 100000+ users sessions at any given time? Will
tomcat be able to efficiently handle a scenario like this? I am also using POJO objects, no
EJB's. Will this be a factor as well? I have been told that beans can be written out of memory as ppulled back in as needed. Does Tomcat handle this? How often does this occur? I should probably have started listing my initial concerns. I am a newbie to
JSF.
Current Specs: JSF 1.2, POJO, Beans attached to component values rather than binding.