Tapestry 5
  1. Tapestry 5
  2. TAP5-455

Allow discarding of persistent field changes for specific strategy only

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 5.0.18
    • Fix Version/s: 5.3
    • Component/s: tapestry-core
    • Labels:
      None

      Description

      Discarding persistent field changes for specific strategies only would be useful for conversational persistent strategies. Currently PersistentFieldManager always iterates over all strategies when discardChanges() is called. Adding discardChanges(String
      strategyName, String pageName) operation to PersistentFieldManager would be enough. See more discussion at http://n2.nabble.com/Discard-persistent-field-changes-for-one-strategy-only--td2179942.html

        Activity

        Kalle Korhonen created issue -
        Kalle Korhonen made changes -
        Field Original Value New Value
        Assignee Kalle Korhonen [ kaosko ]
        Kalle Korhonen made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Fix Version/s 5.3 [ 12316024 ]
        Resolution Fixed [ 1 ]
        Howard M. Lewis Ship made changes -
        Status Resolved [ 5 ] Closed [ 6 ]

          People

          • Assignee:
            Kalle Korhonen
            Reporter:
            Kalle Korhonen
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development