I do actually understand how to get it to work (my example is built using that link). What I’m confused about is that the Select has a “zone” parameter that appears to be ignored (for everything but deciding to do this via ajax). I would expect that the zone parameter would actually update the zone, but that isn’t the case. You have to update the zone via server side addRender.
Just as a newbie it’s confusing and was curious if I’m missing something. It seems like an ajax=“true” would make more sense if it’s not actually going to update. -Lon On Thu, Feb 4, 2016 at 7:36 PM, JumpStart < geoff.callender.jumpst...@gmail.com> wrote: > Here are some working examples that may help. > > T5.4: > > > http://jumpstart.doublenegative.com.au/jumpstart7/examples/ajax/select1 > > T5.3: > > > http://jumpstart.doublenegative.com.au/jumpstart/examples/ajax/select1 > > Geoff > > > On 5 Feb 2016, at 5:54 AM, Lon Varscsak <lon.varsc...@gmail.com> wrote: > > > > I understand that the “zone” parameter makes the Select submit its form > > data via an ajax request. But I’m confused about what it does with the > > “zone” after that is complete. I would expect that the contents of that > > zone be updated, but it doesn’t appear to do that. > > > > If in my onValueChanged* method, I add the zone to the ajax renderer, it > of > > course gets updated. > > > > Am I missing something? > > > > Thanks, > > > > Lon > > > > P.S. — Be gentle, I’m new to Tapestry :P > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
