tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tom van Dijk (JIRA)" <j...@apache.org>
Subject [jira] Commented: (TAP5-1476) Deprecate MultiZoneUpdate, replace with an injectable service to collect zone updates
Date Wed, 16 Mar 2011 15:53:29 GMT

    [ https://issues.apache.org/jira/browse/TAP5-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13007519#comment-13007519
] 

Tom van Dijk commented on TAP5-1476:
------------------------------------

Okay, what if I have an actionLink without a zone parameter and I simply want to update zones
depending on server state?
And what if sometimes I just update no zones at all?

> 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.0
>            Reporter: Howard M. Lewis Ship
>
> 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

Mime
View raw message