Jared Blitzstein

I’ve heard about Wicket a while back but never gave it much consideration. At the time, Spring MVC was the dominent force and I have since used it successfully on a number of projects. However, I now have a greater need for component based development rather than simple action based development. So with that in mind, Wicket rang a bell. I’m going to try and come up with a proof of concept that meets a few criteria:

• Unit testing as a first class citizen
• Ability to use something like SiteMesh to create reusable and modular layouts
• Dynamically decided if a “component” needs to be rendered on a page
• Ability to create a “drop in” component, maybe a trivial weather or time box
• Clean URLs, like /product/king-cobra–s9-right-handed-clubs instead of /product?id=123
  • Search Engine Optimization
  • Url Coding Strategies
• Be friendly with Spring managed services
• Display content based on user role

So with that in mind, I’m going to dive in. More likely than not, I’ll use google to host the code. I’ve used a number of different places like GitHub, Assembla, and even a personal repo, but it seems like Google might be better suited to use from now on.

I’ll be keeping a list of URLs I find on my travels to meet these critera:

• Create RESTful URLs with Wicket
• Wicket extreme consistent URLs
• wicketstuff-annotation (I’m not totally sold on this yet)
• Best Practices

Related posts:

1. My look at Wicket has ended, bad news I’m afraid
2. 5 Days of Wicket
3. Apache Tapestry – Component Classes (Annotated example)
4. Java web developer interview question, do you think this is fair?