I recently began prototyping with Wicket 1.4 for a new customer who is running Websphere Application Server 6.1.  Unfortunately Wicket’s out-of-the-box approach of using filters without a servlet doesn’t work without a tweak.

To get WAS to recognize filters without a backing servlet or JSP, you need to turn on filter compatibility.  Go into the admin console, and select your server.  Choose Web Container Settings, Web Container, Custom Properties.  Add a new property called “com.ibm.ws.webcontainer.invokefilterscompatibility” and set the value to “true.”  Save to the master configuration, restart your server, and you should be good to go.

On a programming note, I hope to be updating this blog more frequently now.  I’d been focusing on my baseball writing over the past year, but I’m spending more time on the technology front.  You may also get some posts on my brand new twins :-).