PS: This tutorial assumes that you are familiar with deploying applications (war files) in Tomcat, setting up datasource\connection pooling using Apache DBCP and in using H2 Database. Objective: Setup two instances of Brix-cms backed by a clustered Jackrabbit JCR on the back-end persisted onto a H2 database. Because there is so much to cover, I will cover the pieces in three installments. Installment #1: What and why of Brix-cms.
Sometimes we need to forward to a servlet or resource that’s outside of Wicket such as a servlet. Here’s how: Modify your web.xml to define your servlet as well as your Wicket application “ignorePaths” init-param: [sourcecode language=“xml”] <?xml version=“1.0” encoding=“UTF-8”?> <!DOCTYPE web-app PUBLIC “-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN” “http://java.sun.com/dtd/web-app_2_3.dtd"> Wicket Example MyApplication org.apache.wicket.protocol.http.WicketFilter applicationClassName com.gu.MyApplication wicket.configuration deployment ignorePaths images/,s/ MyApplication /* SomeServlet com.