advantages that this paradigm can offer us: • Web pages are objects: web pages are not just text files sent back to the client. They are object instances and we can harness OOP to design web pages and with forms. • No complex XML needed: Wicket was designed to minimize the amount of configuration files needed to run our applications. No XML file is required except for the standard deployment descriptor build a quickstart application using Apache Maven. All the artifacts used in the next example (files web.xml, HomePage.class and HomePage.html) are automatically generated by Maven. 4.2.1. Wicket application

advantages that this paradigm can offer us: • Web pages are objects: web pages are not just text files sent back to the client. They are object instances and we can harness OOP to design web pages and with forms. • No complex XML needed: Wicket was designed to minimize the amount of configuration files needed to run our applications. No XML file is required except for the standard deployment descriptor build a quickstart application using Apache Maven. All the artifacts used in the next example (files web.xml, HomePage.class and HomePage.html) are automatically generated by Maven. 4.2.1. Wicket application

advantages that this paradigm can offer us: • Web pages are objects: web pages are not just text files sent back to the client. They are object instances and we can harness OOP to design web pages and with forms. • No complex XML needed: Wicket was designed to minimize the amount of configuration files needed to run our applications. No XML file is required except for the standard deployment descriptor build a quickstart application using Apache Maven. All the artifacts used in the next example (files web.xml, HomePage.class and HomePage.html) are automatically generated by Maven. 4.2.1. Wicket application

advantages that this paradigm can offer us: • Web pages are objects: web pages are not just text files sent back to the client. They are object instances and we can harness OOP to design web pages and with forms. • No complex XML needed: Wicket was designed to minimize the amount of configuration files needed to run our applications. No XML file is required except for the standard deployment descriptor build a quickstart application using Apache Maven. All the artifacts used in the next example (files web.xml, HomePage.class and HomePage.html) are automatically generated by Maven. 4.2.1. Wicket application

dynamic PDF, etc…) and static (JS, CSS, pictures, etc…) Static Resources: usually loaded from files (JS, CSS, pictures, etc…) Header Items: those resources that must be placed in the header section