take care of generating HTML inside the page itself, and we won’t need to use any tag other than standard HTML tags. All we have to do is to attach our components (Java instances) to the HTML tags using amount of configuration files needed to run our applications. No XML file is required except for the standard deployment descriptor web.xml (unless you are using Servlet 3 or a later version. See Chapter 4 string manipulation, security, etc… None 6 wicket-bean-validation Provides support for JSR 303 standard validation. wicket-core wicket-devutils Contains utility classes and components to help developers

take care of generating HTML inside the page itself, and we won’t need to use any tag other than standard HTML tags. All we have to do is to attach our components (Java instances) to the HTML tags using amount of configuration files needed to run our applications. No XML file is required except for the standard deployment descriptor web.xml (unless you are using Servlet 3 or a later version. See Chapter 4 string manipulation, security, etc… None wicket-bean-validation Provides support for JSR 303 standard validation. wicket-core, wicket-tester wicket-devutils Contains utility classes and components

take care of generating HTML inside the page itself, and we won’t need to use any tag other than standard HTML tags. All we have to do is to attach our components (Java instances) to the HTML tags using amount of configuration files needed to run our applications. No XML file is required except for the standard deployment descriptor web.xml (unless you are using Servlet 3 or a later version. See Chapter 4 string manipulation, security, etc… None 6 wicket-bean-validation Provides support for JSR 303 standard validation. wicket-core wicket-devutils Contains utility classes and components to help developers

take care of generating HTML inside the page itself, and we won’t need to use any tag other than standard HTML tags. All we have to do is to attach our components (Java instances) to the HTML tags using amount of configuration files needed to run our applications. No XML file is required except for the standard deployment descriptor web.xml (unless you are using Servlet 3 or a later version. See Chapter 4 designed to work with date and time. wicket-core wicket-bean-validation Provides support for JSR 303 standard validation. wicket-core wicket-devutils Contains utility classes and components to help developers

not 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: 2) We don’t need to run tests for a specifc browser (like we do with Karma) 3) No additional library required, just Wicket and JUnit (no need of browser automation tools like Selenium) Test in isolation