Free.PDF for easy Reference. Getting Started with Apache Wicket. Creating Standard Wicket Components. Covers how to configure the framework.

• Wicket Framework Tutorial

Apache Wicket is a Java-based web application framework that has rapidly grown to be a favorite among many developers. It features a POJO data model, no XML, and a proper mark-up / logic separation not seen in most frameworks. Apache Wicket gives you a simple framework for creating powerful, reusable components and offers an object oriented methodology to web development while requiring only Java and HTML. This Refcard covers Apache Wicket 1.3 and describes common configuration, models, the standard components, implementation of a form, the markup and internationalization options available.

The project layout most typical of Apache Wicket applications is based on the default Maven directories. Any Wicket component that requires view markup in the form of HTML needs to be side-by-side with the Java file. Using Maven however, we can separate the source directories into java/ and resources/ to give some distinction. To get started, download either the wicket-quickstart project and modify it to your needs, or use the maven archetype here: mvn archetype:create -DarchetypeGroupId=org.apache.wicket -DarchetypeArtifactId=wicket-archetype-quickstart -DarchetypeVersion=1.3.5 -DgroupId=com.mysticcoders.refcardmaker -DartifactId=refcardmaker Either way, if using Maven, you’ll need the wicket jar, and the latest slf4j jar.

Org.apache.wicket wicket 1.3.6 org.slf4j slf4j-api 1.4.2. I mentioned that Wicket has no XML, and that’s mostly true, but J2EE requires a web.xml file to do anything. We set up the WicketFilter and point it to our implementation of WebApplication along with the URL mapping. WicketFilter org.apache.wicket.protocol.http. WicketFilter applicationClassName com.mysticcoders.refcardmaker. RefcardApplication filterPath /.

wicketFilter /. Apache Wicket offers a development and deployment mode that can be configured in the web.xml file: configuration development. Earlier sections touched on the order of resource bundles importance from the Page down to Wicket’s default application. Apache Wicket uses the same resource bundles standard in the Java platform, including the naming convention, properties file or XML file.

Wicket Framework Tutorial

Using ResourceBundles, you can pull out messages in your markup using, or use a ResourceModel with the component to pull out the localized text. Another available option is to directly localize the filename of the markup files, i.e. HomePageesMX.html, HomePage.html. Your default locale will be used for HomePage.html, and if you were from Mexico, Wicket would dutifully grab HomePagees MX.html. Recommended Book Wicket in Action is an authoritative, comprehensive guide for Java developers building Wicketbased Web applications. This book starts with an introduction to Wicket’s structure and components, and moves quickly into examples of Wicket at work.

Written by two of the project’s earliest and most authoritative experts, this book shows you both the “how-to” and the “why” of Wicket. As you move through the book, you’ll learn to use and customize Wicket components, how to interact with other technologies like Spring and Hibernate, and how to build rich, Ajax-driven features into your applications.