This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I am developing an application in JSF and saving the state on Client side. The layout of the application has many read only tabs, with no validations but minor adjustments like sorting of tables, highlighting a row etc.
I wonder I have to put all my managed beans into Session scope as many a times I deal only with Output Text only. When the form is submitted the values of the Input Text gets reflected but not of the Output Text. But what JSF mean by Saving State is to save all the components in the form of a Component - Value Tree.
Because the values of output text are not reflected again, I have to literally put all my beans into session scope to work around it. Isn't it a bad design to overload the memory even if it is actually not required.
Is there a workaround, so that it prevents me to put the beans into session.