Page History

...

Ajax support is included in many built-in components and component mixins via the async parameter (in Tapestry 5.4+) and the zone parameter (for earlier versions). Here we use an EventLink component to trigger an Ajax update of another area of the page:

...

• An injected Block or Component to render as the response. The response will be a JSON hash, with a "content" key whose value is the rendered markup. This is the basis for updates with the Zone component.
• The zone's own body (using Zone's getBody() method)
• null (to redraw the current page)
• A JSONObject or JSONArray, which will be sent as the response.
• A StreamResponse, which will be sent as the response.
• A Link, which will send a redirect to the client.
• A page name (as a String), or a page class, or a page instance, which will send a redirect to the indicated page.

See Ajax and Zones See Page Navigation for full descriptions of the above.

...

<t:zone t:id="myzone" id="prop:componentResources.id">

See this JumpStart Example for details.

The show and update function names (Tapestry 5.3 and earlier only) are converted to lower case; all the methods of Tapestry.ElementEffect should have all lower-case names. Because client-side JavaScript is so fluid (new methods may be added to existing objects), Tapestry makes no attempt to validate the function names ... however, if the names are not valid, then the default show and highlight methods will be used.

...

For examples of extending a Form with a Zone and updating multiple zones at once, see the Ajax and ZonesComponents FAQ.

There are also a number of Ajax-related examples at the  Tapestry JumpStart site.

...

The mixin can be configured in a number of ways, see the component reference.

When the user types into the field, the client-side JavaScript will send a request to the server to get completions.

...