. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308 27.2. Create server specific http/2 push support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . frameworks - an overview Component oriented frameworks differ from classic web 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 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

frameworks - an overview Component oriented frameworks differ from classic web 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 You can think of the model as if it was an “inverse” 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 Java and good old HTML: almost all web frameworks force users to adopt 5 special tags or to use server side code inside HTML markup. This is clearly in contrast with the concept of separation between

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295 27.2. Create server specific http/2 push support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . frameworks - an overview Component oriented frameworks differ from classic web 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 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

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294 27.2. Create server specific http/2 push support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . frameworks - an overview Component oriented frameworks differ from classic web 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 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

Introducing Apache Wicket ● Component oriented frameworks difer from classic web frameworks by building a model of requested page on the server side and generating the HTML to send back according to this can think of the model as if it was an “inverse” 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 is a web framework. More precisely is a component-oriented framework. ● Now we gonna look at a classic example of form to sign in a user with a username and password. ● Text felds elements are handled