myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matthias Weßendorf (JIRA) <...@myfaces.apache.org>
Subject [jira] Commented: (TRINIDAD-1772) Allow per page state saving settings
Date Thu, 01 Apr 2010 08:23:27 GMT

    [ https://issues.apache.org/jira/browse/TRINIDAD-1772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12852284#action_12852284
] 

Matthias Weßendorf commented on TRINIDAD-1772:
----------------------------------------------

Design is to introduce a new attribute on <document> (stateSaving).
It takes three values:
-client (force to be (full) client)
-server (force to be server-side)
-default (do what ever the user said in web.xml)

Not this is just _PER_ page, not global...


> Allow per page state saving settings
> ------------------------------------
>
>                 Key: TRINIDAD-1772
>                 URL: https://issues.apache.org/jira/browse/TRINIDAD-1772
>             Project: MyFaces Trinidad
>          Issue Type: New Feature
>    Affects Versions: 2.0.0-alpha-2
>            Reporter: Matthias Weßendorf
>            Assignee: Matthias Weßendorf
>
> JSF/Trinidad state saving is configured via the WEB.xml (see Trinidad config dev-guide).
> However most times we use a hybrid approach (server+token on client), but sometimes you
want a specifc page to be just client-side, to avoid nasty "session expired errors".
> A good example would be a login page, to have (client-only) state.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message