Uploaded image for project: 'Sakai'
  1. Sakai
  2. SAK-25677

Store all JSF STATE on client and not server

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: CLOSED
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 10.0
    • Fix Version/s: 10.0
    • Component/s: Global, JSF
    • Labels:
      None

      Description

      Sakai JSF tools do not consistently store STATE on client or server. We should modify all tools to consistently store STATE on client.

      The property for web.xml: javax.faces.STATE_SAVING_METHOD

      Here is info from documentation:

      Define the state method to be used. There are two different options defined by the specification: "client" and "server" state.
      When "client" state is configured, all state information required to create the tree is embedded within the data rendered to the client. Note that because data received from a remote client must always be treated as "tainted", care must be taken when using such data. Some StateManager implementations may use encryption to ensure that clients cannot modify the data, and that the data received on postback is therefore trustworthy.
      When "server" state is configured, the data is saved somewhere "on the back end", and (at most) a token is embedded in the data rendered to the user.

        Gliffy Diagrams

          Zeplin

            Attachments

            1. CLE-10905.patch
              7 kB
            2. SAK-25677.patch
              12 kB
            3. samigo-jsfviewstate.tiff
              318 kB
            4. screenshot-1.jpg
              screenshot-1.jpg
              296 kB
            5. Screen Shot 2014-03-25 at 1.05.56 AM.png
              Screen Shot 2014-03-25 at 1.05.56 AM.png
              74 kB

              Issue Links

                Activity

                  People

                  Assignee:
                  ottenhoff Sam Ottenhoff
                  Reporter:
                  aaronz Aaron Zeckoski (Inactive)
                  Votes:
                  1 Vote for this issue
                  Watchers:
                  19 Start watching this issue

                    Dates

                    Created:
                    Updated:
                    Resolved:

                      Git Integration