Under the hood of the request processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 9.1. Class Application and request processing . . . . . 52 9.2. Request and Response classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 9.3. The “director” of request processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226 19.5. AJAX request attributes and call listeners . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Under the hood of the request processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 9.1. Class Application and request processing . . . . . 51 9.2. Request and Response classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 9.3. The “director” of request processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 19.5. AJAX request attributes and call listeners . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Under the hood of the request processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 9.1. Class Application and request processing . . . . . 50 9.2. Request and Response classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 9.3. The “director” of request processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 19.5. AJAX request attributes and call listeners . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Under the hood of the request processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 9.1. Class Application and request processing . . . . . 52 9.2. Request and Response classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 9.3. The “director” of request processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226 19.5. AJAX request attributes and call listeners . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

technical point of view, in Wicket a resource is just an implementation of interface org.apache.wicket.request. resource.IResource. ● Working with dynamic resources is less frequent in Wicket and it implies frst time they are requested. ● Resource references are instances of class org.apache.wicket. request.resource.ResourceReference. ● Most of the time static resources are JS or CSS fles which can be getLastResponse. Utility class Mock- HttpServletResponse is returned to extract informations from mocked request. String responseContent = tester.getLastResponse().getDocument(); tester.assertContains("regExp");