. . . . . . 3 3.2. Component oriented frameworks - an overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3.3. Benefits of component oriented frameworks for for web development. . . . . . . . . . . . . . . . . . . . . . . . 4 3.4. Wicket vs the other component oriented frameworks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 6.1. Hiding or disabling a component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . 4 3.2. Component oriented frameworks - an overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 3.3. Benefits of component oriented frameworks for for web development. . . . . . . . . . . . . . . . . . . . . . . . 5 3.4. Wicket vs the other component oriented frameworks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 6.1. Hiding or disabling a component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . 3 3.2. Component oriented frameworks - an overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3.3. Benefits of component oriented frameworks for for web development. . . . . . . . . . . . . . . . . . . . . . . . 4 3.4. Wicket vs the other component oriented frameworks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 6.1. Hiding or disabling a component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . 3 3.2. Component oriented frameworks - an overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3.3. Benefits of component oriented frameworks for for web development. . . . . . . . . . . . . . . . . . . . . . . . 4 3.4. Wicket vs the other component oriented frameworks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 6.1. Hiding or disabling a component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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 model and not vice versa. What is Wicket? ● Wicket 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 Model.of(“Insert username”)); HTML Username: TextField component * The example code for the two versions of the form is available on GitHub under module LoginForm