other Apache project, Wicket is developed paying great attention to user feedback and to suggested features. 4 • Wicket is just about Java and good old HTML: almost all web frameworks force users to adopt in two modes named respectively DEVELOPMENT and DEPLOYMENT. The first mode activates some extra features which help application development, like resources monitoring and reloading, full stack trace rendering of exceptions, an AJAX debugger window, etc… The DEPLOYMENT mode turns off all these features optimizing performances and resource consumption. In our example projects we will use the default

other Apache project, Wicket is developed paying great attention to user feedback and to suggested features. 4 • Wicket is just about Java and good old HTML: almost all web frameworks force users to adopt in two modes named respectively DEVELOPMENT and DEPLOYMENT. The first mode activates some extra features which help application development, like resources monitoring and reloading, full stack trace rendering of exceptions, an AJAX debugger window, etc… The DEPLOYMENT mode turns off all these features optimizing performances and resource consumption. In our example projects we will use the default

other Apache project, Wicket is developed paying great attention to user feedback and to suggested features. 4 • Wicket is just about Java and good old HTML: almost all web frameworks force users to adopt in two modes named respectively DEVELOPMENT and DEPLOYMENT. The first mode activates some extra features which help application development, like resources monitoring and reloading, full stack trace rendering of exceptions, an AJAX debugger window, etc… The DEPLOYMENT mode turns off all these features optimizing performances and resource consumption. In our example projects we will use the default

Apache project, Wicket is developed paying great attention to user feedbacks and to suggested features. • Wicket is just about Java and good old HTML: almost all web frameworks force users to adopt in two modes named respectively DEVELOPMENT and DEPLOYMENT. The first mode activates some extra features which help application development, like resources monitoring and reloading, full stack trace rendering of exceptions, an AJAX debugger window, etc… The DEPLOYMENT mode turns off all these features optimizing performances and resource consumption. In our example projects we will use the default

Model in Wicket 8 ● With Wicket 8 model interface has changed to take advantage of the new syntax features introduced in Java 8. ● In short, IModel has become a functional interface and provides a default behaviors. In Wicket a behaviors are quite like plug-ins that can enrich a component with new features. ● For example org.apache.wicket.ajax.AjaxEventBehavior provides the means to handle an event project, the health of its community is fundamental. ● We have seen some of the most appealing features, still there is lot more to discover! Thank you!