thank you
2013/1/29 Howard Lewis Ship [via Tapestry] <
ml-node+s1045711n5719664...@n5.nabble.com>
> Also, you're seeing some evolution of the framework here, all at once.
>
> The Zone component was pretty early in Tapestry, but the ability to update
> multiple Zone's all in a single request came
Also, you're seeing some evolution of the framework here, all at once.
The Zone component was pretty early in Tapestry, but the ability to update
multiple Zone's all in a single request came later.
The deprecated MultiZoneUpdate object was the older way to update multiple
zones, but it was tediou
If I remember correctly, the first one returns the zone including the
enclosing tags, while the later returns only the zone's body !
Like:
...body...
so the later returns "...body...", while the first one returns the whole
structure:
...body...
So your zone eventually will be:
