Hi guys, I have the following problem: lets suppose I have a managed-bean which should be filled with content by the database if the user requests some certain informations and then the content of this bean should be rendered in the JSF-page. Then, after it is rendered (after the first request) the user can change these informations with forms and if the user clicks on the "save changed informations"-button the hole bean should be "updated" in the database.
If I declare such a bean in the request-scope, the bean will be empty if the user clicks on the submit-button (except the changed values). So this will AFAIK not work. But if I choose "session-scope" the bean will never be killed as long as the user is logged in. This solution is very ugly and - more or less - a memory-leak because I have a lot of beans which should be first loaded with content and then manipulated (= 2x request-scope). Is there a solution to set the scope to "request" but keeping this bean for two or more requests alive? Because session-scope is a unsatisfying option... Greetings, Hendrik
