hood of the request processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 9.1. Class Application and request processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 9.3. The “director” of request processing - RequestCycle. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 12.1. Default form processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

hood of the request processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 9.1. Class Application and request processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 9.3. The “director” of request processing - RequestCycle. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 12.1. Default form processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

hood of the request processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 9.1. Class Application and request processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 9.3. The “director” of request processing - RequestCycle. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 12.1. Default form processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

hood of the request processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 9.1. Class Application and request processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 9.3. The “director” of request processing - RequestCycle. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 12.1. Default form processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

implements links with component org.apache.wicket.markup.html.link.Link, but it's more like onClick event listener than a link: public class HomePage extends WebPage { public HomePage(){ add(new OnLoadHeaderItem(";alert('hello!');"); ● OnEventHeaderItem: execute JavaScript code when a specifc event is triggered. OnEventHeaderItem item = new OnEventHeaderItem("elementId", items meant to work with JavaScript events. In this way we can execute our code only when a specifc event occurs. Bundle resources ● To reduce the number of requests to the server, resources can be aggregated