wood burning stoves 2.0*
The moose likes JSF and the fly likes Usage of org.apache.myfaces.trinidad.CLIENT_STATE_METHOD Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of Murach's Java Servlets and JSP this week in the Servlets forum!
JavaRanch » Java Forums » Java » JSF
Bookmark "Usage of org.apache.myfaces.trinidad.CLIENT_STATE_METHOD" Watch "Usage of org.apache.myfaces.trinidad.CLIENT_STATE_METHOD" New topic

Usage of org.apache.myfaces.trinidad.CLIENT_STATE_METHOD

Sky zhere

Joined: Sep 30, 2009
Posts: 3

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.

I agree. Here's the link: http://aspose.com/file-tools
subject: Usage of org.apache.myfaces.trinidad.CLIENT_STATE_METHOD
Similar Threads
config my-faces & tomahawk & Trinidad
Has anybody got JSF 1.2, Facelets 1.4, Trinidad 1.12 and Spring Security 1.2 working together?
Problem Running MyFaces Trinidad Application
Problem with client side state saving
stylesheet messed up in richfaces JSF page