Tapestry 5
  1. Tapestry 5
  2. TAP5-408

Objects that persist in the session should automatically re-store themselves into the session at the end of the request

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: 5.1.0.0, 5.1, 5.0.15, 5.0.16, 5.0.17, 5.0.18
    • Fix Version/s: 5.1.0.0
    • Component/s: tapestry-core
    • Labels:
      None

      Description

      I talked about this on the mailing list. HttpSession objects have a requirement that if you dirty an object assigned to it, you have to call setAttribute again, to tell the app server the object has been modified.

      Most of the code within Form.java does this properly ( whenever the tracker is modified, it calls setTracker, or _tracker = tracker, etc ).

      It missed one spot, and this is a very small patch to fix it.

      1. form-session.diff
        1 kB
        Fernando Padilla

        Activity

        No work has yet been logged on this issue.

          People

          • Assignee:
            Howard M. Lewis Ship
            Reporter:
            Fernando Padilla
          • Votes:
            3 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development