Tapestry 5
  1. Tapestry 5
  2. TAP5-399

Modified application state objects are not persisted back to the session at the end of the request

    Details

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

      Description

      The fix for TAPESTRY-2595 is incomplete: it is based on the class SessionApplicationStatePersistenceStrategy being registered as an EndOfRequestListener with the EndOfRequestListenerHub. This is not done, thus the strategy never gets a chance to locate modified ASOs and re-write them into the session.

      Modified ASOs need to be stored back into the session at the end of the request to ensure that any changes are propagated to other servers in the cluster.

        Activity

        There are no comments yet on this issue.

          People

          • Assignee:
            Howard M. Lewis Ship
            Reporter:
            Howard M. Lewis Ship
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development