Tapestry
  1. Tapestry
  2. TAPESTRY-2595

Application State Objects are not persisted back to the session at the end of the request

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 5.0.14
    • Fix Version/s: 5.0.15
    • Component/s: tapestry-core
    • Labels:
      None

      Description

      For proper behavior in a cluster, ASOs should be updated back into the session at the end of each request, otherwise there's no guarantee that the ASO data will be replicated across a cluster.

      Ideally, this should have an optimization, such that an ASO that is not "dirty" is not stored. This would take the form of an optional interface.

        Activity

        Howard M. Lewis Ship created issue -
        Howard M. Lewis Ship made changes -
        Field Original Value New Value
        Status Open [ 1 ] In Progress [ 3 ]
        Howard M. Lewis Ship made changes -
        Status In Progress [ 3 ] Closed [ 6 ]
        Fix Version/s 5.0.15 [ 12313350 ]
        Resolution Fixed [ 1 ]
        Mark Thomas made changes -
        Workflow jira [ 12437603 ] Default workflow, editable Closed status [ 12568796 ]
        Mark Thomas made changes -
        Workflow Default workflow, editable Closed status [ 12568796 ] jira [ 12591831 ]

          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