• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

To Authors - JSF session issue

 
Greenhorn
Posts: 15
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi David,

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.

Thanks...
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic