. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241 21.3. Client-side APIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . frameworks in that they build a model of requested pages on 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. it is built on the server-side 2. it is built before HTML is sent to the client 3. HTML code is generated using this model and not vice versa. General schema of page request handling

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228 21.3. Client-side APIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . frameworks in that they build a model of requested pages on 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. it is built on the server-side 2. it is built before HTML is sent to the client 3. HTML code is generated using this model and not vice versa. General schema of page request handling

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227 21.3. Client-side APIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . frameworks in that they build a model of requested pages on 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. it is built on the server-side 2. it is built before HTML is sent to the client 3. HTML code is generated using this model and not vice versa. General schema of page request handling

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241 21.3. Client-side APIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . frameworks in that they build a model of requested page on 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 JavaScript DOM, meaning that: 1. is built on server-side 2. is built before HTML is sent to client 3. HTML code is generated using this model and not vice versa. image::../img/requesthandling-general.png[]

JavaScript DOM, meaning that: 1) is built on server-side 2) is built before HTML is sent to client 3) HTML code is generated using this model and not vice versa. What is Wicket? ● Wicket is a ● By default after onClick has been executed, Wicket will send back to the current page to the client web browser. If we want to navigate to another page we must use method setResponsePage of class dynamic resources (those who returns they value on the fly [ex: a RSS]). ● From a technical point of view, in Wicket a resource is just an implementation of interface org.apache.wicket.request. resource