← Playground index

Server-side update targeting

Here the server decides which containers refresh - the action calls AjaxUpdater.triggerUpdate("id", context()) for each target and returns null. The client never declares an updateContainerID. This is the idiom real apps use (fire two named containers; or fire a set minus the current one).

NB pattern: action refreshes two named siblings

Scrabble pattern: refresh a set, minus the current container

The triggering link is inside allBox1, which the action drops from its set (it is refreshed by the click itself) and fires allBox2 + allBox3 server-side.