. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 9.1. Class Application and request processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312 28.1. Example setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . web development the same kind of abstraction that GUI frameworks offer when we build a desktop application. Most of those kind of frameworks hide the details of the HTTP protocol and naturally solve the

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 9.1. Class Application and request processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299 28.1. Example setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . web development the same kind of abstraction that GUI frameworks offer when we build a desktop application. Most of those kind of frameworks hide the details of the HTTP protocol and naturally solve the

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 9.1. Class Application and request processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298 28.1. Example setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . web development the same kind of abstraction that GUI frameworks offer when we build a desktop application. Most of those kind of frameworks hide the details of the HTTP protocol and naturally solve the

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 9.1. Class Application and request processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309 27.1. Example setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . web development the same kind of abstraction that GUI frameworks offer when we build a desktop application. Most of those kind of frameworks hide the details of the HTTP protocol and naturally solve the

web development the same kind of abstraction that GUI frameworks ofer when we build a desktop application. ● This kind of framework hides the details of the HTTP protocol and naturally solves the problem just HTML (pictures, properties fle, etc...) Where is the HTML? ● A Wicket application is a standard Java EE web application, hence it is deployed through a web.xml fle placed inside folder WEB-INF: version="1.0" encoding="UTF-8"?> Application 2.3//EN" "http://java.sun.com/dtd/web-app_2_3.dtd"> Wicket