• 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

Usage of org.apache.myfaces.trinidad.CLIENT_STATE_METHOD

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

I am new to JSF and trying to use the Trinidad JSF implementation.

In my Application the standard JSF <context-param> javax.faces.STATE_SAVING_METHOD is set to "client". Based on this tag I have come across the Trinidad "org.apache.myfaces.trinidad.CLIENT_STATE_METHOD" context-param.

From the Trinidad documentation I understand that the default value of "token" will store the page state in the HttpSession and setting its value to "all" will store it in the client side in a hidden field.

I want to know what is the policy Trinidad adopts for saving page state ( if at all ) when I set the standard JSF context-param javax.faces.STATE_SAVING_METHOD to "client" but do not use the Trinidad specific "org.apache.myfaces.trinidad.CLIENT_STATE_METHOD" tag in web.xml. What are the affects of having such a setting in my application specially related to performance.

Cheers!!
 
What could go wrong in a swell place like "The Evil Eye"? Or with this tiny ad?
a bit of art, as a gift, that will fit in a stocking
https://gardener-gift.com
reply
    Bookmark Topic Watch Topic
  • New Topic