In the past 2 years I worked in, and visited many development teams to help them implement divers Wicket applications. Some applications were mostly for visualizing stuff, some were full of forms, and some were full of Ajax tricks. This article contains some of the lessons I had to teach, or had to learn myself. I’ll present them as do’s and dont’s. They are:

• Do use models
• Don’t use an Ajax library without intimate knowledge of the library
• Do make sure you understand the repeaters for high performance sites
• Don’t overuse inheritance
• Do keep markup in sync with the component code
• Don’t try to do authorization from a servlet filter
• Do take your time to override key Wicket features

Read the rest of this entry »