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 for more details). 5 Chapter 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 hence it is deployed through a web.xml file placed inside folder WEB-INF: Illustration: The standard directory structure of a Wicket application The content of web.xml declares a servlet filter (class

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 for more details). 6 Chapter 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 hence it is deployed through a web.xml file placed inside folder WEB-INF: Illustration : The standard directory structure of a Wicket application The content of web.xml declares a servlet filter (class

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 for more details). 5 Chapter 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 hence it is deployed through a web.xml file placed inside folder WEB-INF: Illustration: The standard directory structure of a Wicket application The content of web.xml declares a servlet filter (class

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 for more details). 5 Chapter 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 hence it is deployed through a web.xml file placed inside folder WEB-INF: Illustration: The standard directory structure of a Wicket application The content of web.xml declares a servlet filter (class

● A Wicket application is a standard Java EE web application, hence it is deployed through a web.xml fle placed inside folder WEB-INF: /* The web.xml file package helloWorld; import org.apache.wicket.Page; import org.apache.wicket.protocol.http getHomePage() { return HomePage.class; } @Override Public init(){...} } ● If we look back at web.xml we can see that we have provided the Wicket flter with a parameter called applicationClassName.