Good question. I think it may be an historical accident, made largely redundant by AjaxResponseRenderer, and MultiZoneUpdate before it. They take no notice of what was specified in the component's zone parameter. With AjaxResponseRenderer you don't even have to return a zone - instead you could return a call to JavaScript.
I like it the newer way, so in the client I use zone="^" wherever possible, as opposed to specifying a zone name, and in the server I use AjaxResponseRenderer, as opposed to returning a Zone's body. This way, the only purpose of the zone parameter is tell Tapestry to use AJAX. Perhaps it's time for Tapestry to replace the zone parameter with ajax="true" or xhr="true"? Geoff On 14 Oct 2014, at 4:43 am, Muhammad Gelbana <m.gelb...@gmail.com> wrote: > Anyone please ? Is my question unclear ? > > *---------------------* > *Muhammad Gelbana* > http://www.linkedin.com/in/mgelbana > > On Mon, Oct 13, 2014 at 8:34 AM, Muhammad Gelbana <m.gelb...@gmail.com> > wrote: > >> I have a *Select* component. I need to display a *Zone* when the *Select* >> component is rendered so I specified the zone's ID in the select >> component's *t:zone* attribute. >> >> But I still have to explicitly render the zone >> >> >>> ajax.addRender( >>> myZone >>> ); >> >> >> I even removed the *Select* component's *VALUE_CHANGED* event handler >> assuming that having it would override this default\expected behavior but >> it didn't work. >> >> I believe that specifying the zone ID once in the tml is enough to know >> what zone should be displayed on a *VALUE_CHANGED* event. Also having a >> way to override this default behavior in the *VALUE_CHANGED* event >> handler method will definitely be needed. >> >> So should I specify the zone twice for the exact purpose ? Or is there a >> cleaner way to do it ? >> *---------------------* >> *Muhammad Gelbana* >> http://www.linkedin.com/in/mgelbana >> --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
