Uploaded image for project: 'Tapestry 5'
  1. Tapestry 5
  2. TAP5-1476

Deprecate MultiZoneUpdate, replace with an injectable service to collect zone updates

    Details

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

      Description

      MultiZoneUpdate presumes that there's a single place where all the zone to be updated are known. This is not necessarilly the case.

      I'd like to see something like:

      @Inject
      private ZoneUpdater zoneUpdater();

      Object onSuccess()
      {
      zoneUpdater.update("foo", fooBlock);
      zoneUpdater.update("bar", barBlock);

      return myZone.getBody();
      }

      The main point here is that different event handlers would all be able to invoke ZoneUpdater.update() .

      This would also allow a single response to render main content (for the requesting Zone on the client) plus zone updates to named zones.

        Attachments

          Activity

            People

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

              Dates

              • Created:
                Updated:
                Resolved: