. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 4.2. Configuration of Wicket applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268 24.1. Configuration of the runtime environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268 24.2. Configuration of the JUnit based integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295 27.2. Create server specific http/2 push support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 4.2. Configuration of Wicket applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267 24.1. Configuration of the runtime environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267 24.2. Configuration of the JUnit based integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294 27.2. Create server specific http/2 push support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 4.2. Configuration of Wicket applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279 24.1. Configuration of the runtime environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279 24.2. Configuration of the JUnit based integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308 27.2. Create server specific http/2 push support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 4.2. Configuration of Wicket applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280 24.1. Configuration of the runtime environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280 24.2. Configuration of the JUnit based integration the server side and the HTML sent back to the client is generated according to this model. You can think of the model as if it was an “inverse” JavaScript DOM, meaning that: 1. is built on server-side

on the server side and generating the HTML to send back according to this model. You can think of the model as if it was an “inverse” JavaScript DOM, meaning that: 1) is built on server-side 2) represents our web application built with Wicket and it's responsible for confguring it when the server is starting up. ● Class Application comes with a set of confguration methods that we can override code only when a specifc event occurs. Bundle resources ● To reduce the number of requests to the server, resources can be aggregated in bundles. A resource bundle can be declared during application