[
https://issues.apache.org/jira/browse/TAP5-1407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Stanton updated TAP5-1407:
-------------------------------
Fix Version/s: 5.2.4
Description:
Currently MultiZoneUpdate is a chain of MultiZoneUpdates, ie
public class MultiZoneUpdate
{
...
public MultiZoneUpdate add(String zoneId, Object renderer)
{
return new MultiZoneUpdate(zoneId, renderer, this);
}
...
}
usage:
MultiZoneUpdate mzu = new MultiZoneUpdate("zone2", zone1);
mzu = mzu.add("zone2", zone2);
mzu = mzu.add("zone3", zone3);
...
return mzu;
This becomes hard to use when event handlers call common methods which
contribute zone updates.
Also, it is possible to request multiple updates for the one zone which doesn't
make much sense.
In some cases it would be much easier if you could construct a MultiZoneUpdate
object without actually contributing a zone update directive. ie:
MultiZoneUpdate mzu = new MultiZoneUpdate();
mzu.add("zone2", zone1);
mzu.add("zone2", zone2);
mzu.add("zone3", zone3);
...
return mzu;
was:
Currently MultiZoneUpdate is a chain of MultiZoneUpdates, ie
MultiZoneUpdate mzu = new MultiZoneUpdate("zone2", zone1);
mzu.add("zone2", zone2);
mzu.add("zone3", zone3);
...
return mzu;
This becomes hard to use when event handlers call common methods which
contribute zone updates.
Also, it is possible to request multiple updates for the one zone which doesn't
make much sense.
In some cases it would be much easier if you could construct a MultiZoneUpdate
object without actually contributing a zone update directive. ie:
MultiZoneUpdate mzu = new MultiZoneUpdate();
mzu.add("zone2", zone1);
mzu.add("zone2", zone2);
mzu.add("zone3", zone3);
...
return mzu;
> multizoneupdate should be easier to use - not a chain
> -----------------------------------------------------
>
> Key: TAP5-1407
> URL: https://issues.apache.org/jira/browse/TAP5-1407
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.2.4
> Reporter: Paul Stanton
> Fix For: 5.2.4
>
>
> Currently MultiZoneUpdate is a chain of MultiZoneUpdates, ie
> public class MultiZoneUpdate
> {
> ...
> public MultiZoneUpdate add(String zoneId, Object renderer)
> {
> return new MultiZoneUpdate(zoneId, renderer, this);
> }
> ...
> }
> usage:
> MultiZoneUpdate mzu = new MultiZoneUpdate("zone2", zone1);
> mzu = mzu.add("zone2", zone2);
> mzu = mzu.add("zone3", zone3);
> ...
> return mzu;
> This becomes hard to use when event handlers call common methods which
> contribute zone updates.
> Also, it is possible to request multiple updates for the one zone which
> doesn't make much sense.
> In some cases it would be much easier if you could construct a
> MultiZoneUpdate object without actually contributing a zone update directive.
> ie:
> MultiZoneUpdate mzu = new MultiZoneUpdate();
> mzu.add("zone2", zone1);
> mzu.add("zone2", zone2);
> mzu.add("zone3", zone3);
> ...
> return mzu;
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
