[ https://issues.apache.org/jira/browse/TAP5-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship reassigned TAP5-1476: ------------------------------------------ Assignee: Howard M. Lewis Ship > Deprecate MultiZoneUpdate, replace with an injectable service to collect zone > updates > ------------------------------------------------------------------------------------- > > Key: TAP5-1476 > URL: https://issues.apache.org/jira/browse/TAP5-1476 > Project: Tapestry 5 > Issue Type: Improvement > Components: tapestry-core > Affects Versions: 5.3 > Reporter: Howard M. Lewis Ship > Assignee: Howard M. Lewis Ship > Attachments: zone-updater.patch, > zone_updater_with_zone-updater_as_return.patch, > zone_updater_with_zone-updater_as_return.patch > > > 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. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira