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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 9.5. Exception handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 9.5. Exception handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 9.5. Exception handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 9.5. Exception handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

forms and models see the user guide: https://wicket.apache.org/learn/#guide Resource handling Resource handling ● With “resource” we indicate both static resources (such as JS and CSS fles) and dynamic apache.wicket.request. resource.IResource. ● Working with dynamic resources is less frequent in Wicket and it implies a custom implementation of IResource. ● On the contrary handling static resources 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