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

        Hide
        Massimo Lusetti added a comment -

        Kalle does this still applicable ?

        Show
        Massimo Lusetti added a comment - Kalle does this still applicable ?
        Hide
        Kalle Korhonen added a comment -

        Yes, I'm gonna take this, it's an easy addition.

        Show
        Kalle Korhonen added a comment - Yes, I'm gonna take this, it's an easy addition.

          People

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

            Dates

            • Created:
              Updated:
              Resolved:

              Development